Systems and methods for anticipatory locking and unlocking of a smart-sensor door lock

ABSTRACT

An electronic device associated with a lock device obtains a number of users detected within a premises, and detects a trigger event related to a lock device and premises. When the trigger event is detected, a target state of the lock device is determined based on: (1) the number of users within the premises, and (2) user security profiles indicating a desired target state of the lock device when a respective user is within the premises. A current state of the lock device is determined, and if the current state and the target state of the lock device are not the same, instructions are provided to the lock device based on the target state.

RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.14/726,144, filed May 29, 2015, entitled “Systems and Methods forAnticipatory Locking and Unlocking of a Smart-Sensor Door Lock,” whichis hereby incorporated by reference in its entirety.

TECHNICAL FIELD

This relates generally to smart door locks, including but not limited tomethods and systems for automatically locking and unlocking doors basedon a variety of factors.

BACKGROUND

Electronic door locks offer the convenience of locking and unlockingdoors without requiring a user to physically turn a key. Some electronicdoor locks include electromechanical components, such as battery-poweredmotors for actuating and retracting the bolt of the door lock.Consequently, electronic door locks have substantial limitations withrespect to power consumption, particularly given the typical frequencywith which electronic door locks are operated on a daily basis.

SUMMARY

Accordingly, there is a need for methods, systems, and interfaces forautomatically determining a target state of a lock device when a triggerevent is detected, and locking or unlocking the lock device accordingly.By utilizing inputs retrieved from one or more devices, such as smartdevices with sensory capabilities positioned throughout an environment,a target state of the lock device is determined (e.g., locked/unlockedstate) and instructions based on the determined target state areprovided to the lock device if needed. Thus, the bolt of a lock deviceis actuated or retracted only if determined to be necessary—otherwise,the lock device maintains its current state. Average power consumptionis therefore reduced while maintaining the advantages of typicalelectronic door locks.

In accordance with some implementations, a method is performed at anelectronic device (e.g., a smart device in a smart home network) withone or more processors and memory storing instructions for execution bythe one or more processors, wherein the electronic device is associatedwith a lock device. The method includes obtaining a number of usersdetected within a premises, and detecting a trigger event related to thelock device and the premises. When the trigger event is detected, atarget state of the lock device is determined based on at least one of aplurality of factors. Factors include: (1) the obtained number of usersdetected within the premises, (2) respective security profiles of theone or more detected users, wherein a respective security profile of arespective user indicates a desired target state of the lock device whenthe respective user is within the premises, (3) a location of the one ormore detected users; (4) a user state of the one or more detected users,wherein a respective user state of a respective user indicates that therespective user is asleep or active; and (5) a current premises mode,including an armed state and a disarmed state. A current state of thelock device is determined, and if the current state of the lock deviceand the target state of the lock device are not the same, instructionsare provided to the lock device based on the target state of the lockdevice.

In accordance with some implementations, an electronic device (e.g., asmart device in a smart home network) includes one or more processors,memory, and one or more programs; the one or more programs are stored inthe memory and configured to be executed by the one or more processors.The one or more programs include instructions for performing theoperations of the method described above. In accordance with someimplementations, a non-transitory computer-readable storage medium hasstored therein instructions that, when executed by the electronicdevice, cause the electronic device to perform the operations of themethod described above.

Thus, electronic devices are provided with more effective and efficientmethods for automatically determining a target state of a lock devicewhen a trigger event is detected, and locking or unlocking the lockdevice accordingly, thereby increasing the effectiveness and efficiencyof such devices and systems.

BRIEF DESCRIPTION OF THE DRAWINGS

For a better understanding of the various described implementations,reference should be made to the Description of Implementations below, inconjunction with the following drawings in which like reference numeralsrefer to corresponding parts throughout the figures.

FIG. 1 is an example smart home environment, in accordance with someimplementations.

FIG. 2 is a block diagram illustrating an example network architecturethat includes a smart home network, in accordance with someimplementations.

FIG. 3 illustrates a network-level view of an extensible devices andservices platform with which the smart home environment of FIG. 1 isintegrated, in accordance with some implementations.

FIG. 4 illustrates an abstracted functional view of the extensibledevices and services platform of FIG. 3, with reference to a processingengine as well as devices of the smart home environment, in accordancewith some implementations.

FIG. 5 is a representative operating environment in which a hub deviceserver system interacts with client devices and hub devicescommunicatively coupled to local smart devices, in accordance with someimplementations.

FIG. 6 is a block diagram illustrating a representative hub device, inaccordance with some implementations.

FIG. 7 is a block diagram illustrating a representative hub serversystem, in accordance with some implementations.

FIG. 8 is a block diagram illustrating a representative client deviceassociated with a user account, in accordance with some implementations.

FIG. 9 is a block diagram illustrating a representative smart device, inaccordance with some implementations.

FIG. 10 is a block diagram illustrating a representative smart homeprovider server system, in accordance with some implementations.

FIG. 11 is an example smart home environment, in accordance with someimplementations.

FIG. 12 illustrates various states of a lock device, in accordance withsome implementations.

FIGS. 13A-13C illustrate examples of graphical user interfaces fordisplaying notifications, sending commands, and managing a securityprofile, in accordance with some implementations.

FIGS. 14A-14D are flow diagrams illustrating a method of automaticallydetermining a target state of a lock device in response to detecting atrigger event, in accordance with some implementations.

Like reference numerals refer to corresponding parts throughout theseveral views of the drawings.

DESCRIPTION OF IMPLEMENTATIONS

Reference will now be made in detail to implementations, examples ofwhich are illustrated in the accompanying drawings. In the followingdetailed description, numerous specific details are set forth in orderto provide a thorough understanding of the various describedimplementations. However, it will be apparent to one of ordinary skillin the art that the various described implementations may be practicedwithout these specific details. In other instances, well-known methods,procedures, components, circuits, and networks have not been describedin detail so as not to unnecessarily obscure aspects of theimplementations.

It will also be understood that, although the terms first, second, etc.are, in some instances, used herein to describe various elements, theseelements should not be limited by these terms. These terms are only usedto distinguish one element from another. For example, a first unlockedstate could be termed a second unlocked state, and, similarly, a secondunlocked state could be termed a first unlocked state, without departingfrom the scope of the various described implementations. The firstunlocked state and the second unlocked state are both unlocked states,but they are not the same unlocked state.

The terminology used in the description of the various describedimplementations herein is for the purpose of describing particularimplementations only and is not intended to be limiting. As used in thedescription of the various described implementations and the appendedclaims, the singular forms “a”, “an” and “the” are intended to includethe plural forms as well, unless the context clearly indicatesotherwise. It will also be understood that the term “and/or” as usedherein refers to and encompasses any and all possible combinations ofone or more of the associated listed items. It will be furtherunderstood that the terms “includes,” “including,” “comprises,” and/or“comprising,” when used in this specification, specify the presence ofstated features, integers, steps, operations, elements, and/orcomponents, but do not preclude the presence or addition of one or moreother features, integers, steps, operations, elements, components,and/or groups thereof.

As used herein, the term “if” is, optionally, construed to mean “when”or “upon” or “in response to determining” or “in response to detecting”or “in accordance with a determination that,” depending on the context.Similarly, the phrase “if it is determined” or “if [a stated conditionor event] is detected” is, optionally, construed to mean “upondetermining” or “in response to determining” or “upon detecting [thestated condition or event]” or “in response to detecting [the statedcondition or event]” or “in accordance with a determination that [astated condition or event] is detected,” depending on the context.

It is to be appreciated that “smart home environments” may refer tosmart environments for homes such as a single-family house, but thescope of the present teachings is not so limited. The present teachingsare also applicable, without limitation, to duplexes, townhomes,multi-unit apartment buildings, hotels, retail stores, office buildings,industrial buildings, and more generally any living space or work space.Moreover, the techniques and methods disclosed herein can be used forlocks other than locks for buildings, such as safes, storage units, toolboxes, gun cases, or security devices (e.g., bike locks, etc.).

It is also to be appreciated that while the terms user, customer,installer, homeowner, occupant, guest, tenant, landlord, repair person,and the like may be used to refer to the person or persons acting in thecontext of some particularly situations described herein, thesereferences do not limit the scope of the present teachings with respectto the person or persons who are performing such actions. Thus, forexample, the terms user, customer, purchaser, installer, subscriber, andhomeowner may often refer to the same person in the case of asingle-family residential dwelling, because the head of the household isoften the person who makes the purchasing decision, buys the unit, andinstalls and configures the unit, and is also one of the users of theunit. However, in other scenarios, such as a landlord-tenantenvironment, the customer may be the landlord with respect to purchasingthe unit, the installer may be a local apartment supervisor, a firstuser may be the tenant, and a second user may again be the landlord withrespect to remote control functionality. Importantly, while the identityof the person performing the action may be germane to a particularadvantage provided by one or more of the implementations, such identityshould not be construed in the descriptions that follow as necessarilylimiting the scope of the present teachings to those particularindividuals having those particular identities.

FIG. 1 is an example smart home environment 100 in accordance with someimplementations. Smart home environment 100 includes a structure 150(e.g., a house, office building, garage, or mobile home) with variousintegrated devices. It will be appreciated that devices may also beintegrated into a smart home environment 100 that does not include anentire structure 150, such as an apartment, condominium, or officespace. Further, the smart home environment 100 may control and/or becoupled to devices outside of the actual structure 150. Indeed, severaldevices in the smart home environment 100 need not be physically withinthe structure 150. For example, a device controlling a pool heater 114or irrigation system 116 may be located outside of the structure 150.

The depicted structure 150 includes a plurality of rooms 152, separatedat least partly from each other via walls 154. The walls 154 may includeinterior walls or exterior walls. Each room may further include a floor156 and a ceiling 158. Devices may be mounted on, integrated with and/orsupported by a wall 154, floor 156 or ceiling 158.

In some implementations, the integrated devices of the smart homeenvironment 100 include intelligent, multi-sensing, network-connecteddevices that integrate seamlessly with each other in a smart homenetwork (e.g., 202 FIG. 2) and/or with a central server or acloud-computing system to provide a variety of useful smart homefunctions. The smart home environment 100 may include one or moreintelligent, multi-sensing, network-connected thermostats 102(hereinafter referred to as “smart thermostats 102”), one or moreintelligent, network-connected, multi-sensing hazard detection units 104(hereinafter referred to as “smart hazard detectors 104”), one or moreintelligent, multi-sensing, network-connected entryway interface devices106 and 120 (hereinafter referred to as “smart doorbells 106” and “smartdoor locks 120”), and one or more intelligent, multi-sensing,network-connected alarm systems 122 (hereinafter referred to as “smartalarm systems 122”).

In some implementations, the one or more smart thermostats 102 detectambient climate characteristics (e.g., temperature and/or humidity) andcontrol a HVAC system 103 accordingly. For example, a respective smartthermostat 102 includes an ambient temperature sensor.

The one or more smart hazard detectors 104 may include thermal radiationsensors directed at respective heat sources (e.g., a stove, oven, otherappliances, a fireplace, etc.). For example, a smart hazard detector 104in a kitchen 153 includes a thermal radiation sensor directed at astove/oven 112. A thermal radiation sensor may determine the temperatureof the respective heat source (or a portion thereof) at which it isdirected and may provide corresponding blackbody radiation data asoutput.

The smart doorbell 106 and/or the smart door lock 120 may detect aperson's approach to or departure from a location (e.g., an outer door),control doorbell/door locking functionality (e.g., receive user inputsfrom a portable electronic device 166-1 to actuate bolt of the smartdoor lock 120), announce a person's approach or departure via audio orvisual means, and/or control settings on a security system (e.g., toactivate or deactivate the security system when occupants go and come).

The smart alarm system 122 may detect the presence of an individualwithin close proximity (e.g., using built-in IR sensors), sound an alarm(e.g., through a built-in speaker, or by sending commands to one or moreexternal speakers), and send notifications to entities or userswithin/outside of the smart home network 100. In some implementations,the smart alarm system 122 also includes one or more input devices orsensors (e.g., keypad, biometric scanner, NFC transceiver, microphone)for verifying the identity of a user, and one or more output devices(e.g., display, speaker). In some implementations, the smart alarmsystem 122 may also be set to an “armed” mode, such that detection of atrigger condition or event causes the alarm to be sounded unless adisarming action is performed.

In some implementations, the smart home environment 100 includes one ormore intelligent, multi-sensing, network-connected wall switches 108(hereinafter referred to as “smart wall switches 108”), along with oneor more intelligent, multi-sensing, network-connected wall pluginterfaces 110 (hereinafter referred to as “smart wall plugs 110”). Thesmart wall switches 108 may detect ambient lighting conditions, detectroom-occupancy states, and control a power and/or dim state of one ormore lights. In some instances, smart wall switches 108 may also controla power state or speed of a fan, such as a ceiling fan. The smart wallplugs 110 may detect occupancy of a room or enclosure and control supplyof power to one or more wall plugs (e.g., such that power is notsupplied to the plug if nobody is at home).

In some implementations, the smart home environment 100 of FIG. 1includes a plurality of intelligent, multi-sensing, network-connectedappliances 112 (hereinafter referred to as “smart appliances 112”), suchas refrigerators, stoves, ovens, televisions, washers, dryers, lights,stereos, intercom systems, garage-door openers, floor fans, ceilingfans, wall air conditioners, pool heaters, irrigation systems, securitysystems, space heaters, window AC units, motorized duct vents, and soforth. In some implementations, when plugged in, an appliance mayannounce itself to the smart home network, such as by indicating whattype of appliance it is, and it may automatically integrate with thecontrols of the smart home. Such communication by the appliance to thesmart home may be facilitated by either a wired or wirelesscommunication protocol. The smart home may also include a variety ofnon-communicating legacy appliances 140, such as old conventionalwasher/dryers, refrigerators, and the like, which may be controlled bysmart wall plugs 110. The smart home environment 100 may further includea variety of partially communicating legacy appliances 142, such asinfrared (“IR”) controlled wall air conditioners or other IR-controlleddevices, which may be controlled by IR signals provided by the smarthazard detectors 104 or the smart wall switches 108.

In some implementations, the smart home environment 100 includes one ormore network-connected cameras 118 that are configured to provide videomonitoring and security in the smart home environment 100. The cameras118 may be used to determine occupancy of the structure 150 and/orparticular rooms 152 in the structure 150, and thus may act as occupancysensors. For example, video captured by the cameras 118 may be processedto identify the presence of an occupant in the structure 150 (e.g., in aparticular room 152). Specific individuals may be identified based, forexample, on their appearance (e.g., height, face) and/or movement (e.g.,their walk/gait). Cameras 118 may additionally include one or moresensors (e.g., IR sensors, motion detectors), input devices (e.g.,microphone for capturing audio), and output devices (e.g., speaker foroutputting audio).

The smart home environment 100 may additionally or alternatively includeone or more other occupancy sensors (e.g., the smart doorbell 106, smartdoor locks 120, touch screens, IR sensors, microphones, ambient lightsensors, motion detectors, smart nightlights 170, etc.). In someimplementations, the smart home environment 100 includes radio-frequencyidentification (RFID) readers (e.g., in each room 152 or a portionthereof) that determine occupancy based on RFID tags located on orembedded in occupants. For example, RFID readers may be integrated intothe smart hazard detectors 104.

The smart home environment 100 may also include communication withdevices outside of the physical home but within a proximate geographicalrange of the home. For example, the smart home environment 100 mayinclude a pool heater monitor 114 that communicates a current pooltemperature to other devices within the smart home environment 100and/or receives commands for controlling the pool temperature.Similarly, the smart home environment 100 may include an irrigationmonitor 116 that communicates information regarding irrigation systemswithin the smart home environment 100 and/or receives controlinformation for controlling such irrigation systems.

By virtue of network connectivity, one or more of the smart home devicesof FIG. 1 may further allow a user to interact with the device even ifthe user is not proximate to the device. For example, a user maycommunicate with a device using a computer (e.g., a desktop computer,laptop computer, or tablet) or other portable electronic device 166(e.g., a mobile phone, such as a smart phone). A webpage or applicationmay be configured to receive communications from the user and controlthe device based on the communications and/or to present informationabout the device's operation to the user. For example, the user may viewa current set point temperature for a device (e.g., a stove) and adjustit using a computer. The user may be in the structure during this remotecommunication or outside the structure.

As discussed above, users may control smart devices in the smart homeenvironment 100 using a network-connected computer or portableelectronic device 166. In some examples, some or all of the occupants(e.g., individuals who live in the home) may register their device 166with the smart home environment 100. Such registration may be made at acentral server to authenticate the occupant and/or the device as beingassociated with the home and to give permission to the occupant to usethe device to control the smart devices in the home. An occupant may usetheir registered device 166 to remotely control the smart devices of thehome, such as when the occupant is at work or on vacation. The occupantmay also use their registered device to control the smart devices whenthe occupant is actually located inside the home, such as when theoccupant is sitting on a couch inside the home. It should be appreciatedthat instead of or in addition to registering devices 166, the smarthome environment 100 may make inferences about which individuals live inthe home and are therefore occupants and which devices 166 areassociated with those individuals. As such, the smart home environmentmay “learn” who is an occupant and permit the devices 166 associatedwith those individuals to control the smart devices of the home.

In some implementations, in addition to containing processing andsensing capabilities, devices 102, 104, 106, 108, 110, 112, 114, 116,118, 120, and/or 122 (collectively referred to as “the smart devices”)are capable of data communications and information sharing with othersmart devices, a central server or cloud-computing system, and/or otherdevices that are network-connected. Data communications may be carriedout using any of a variety of custom or standard wireless protocols(e.g., IEEE 802.15.4, Wi-Fi, ZigBee, 6LoWPAN, Thread, Z-Wave, BluetoothSmart, ISA100.11a, WirelessHART, MiWi, etc.) and/or any of a variety ofcustom or standard wired protocols (e.g., Ethernet, HomePlug, etc.), orany other suitable communication protocol, including communicationprotocols not yet developed as of the filing date of this document.

In some implementations, the smart devices serve as wireless or wiredrepeaters. In some implementations, a first one of the smart devicescommunicates with a second one of the smart devices via a wirelessrouter. The smart devices may further communicate with each other via aconnection (e.g., network interface 160) to a network, such as theInternet 162. Through the Internet 162, the smart devices maycommunicate with a smart home provider server system 164 (also called acentral server system and/or a cloud-computing system herein). The smarthome provider server system 164 may be associated with a manufacturer,support entity, or service provider associated with the smart device(s).In some implementations, a user is able to contact customer supportusing a smart device itself rather than needing to use othercommunication means, such as a telephone or Internet-connected computer.In some implementations, software updates are automatically sent fromthe smart home provider server system 164 to smart devices (e.g., whenavailable, when purchased, or at routine intervals).

In some implementations, the network interface 160 includes aconventional network device (e.g., a router), and the smart homeenvironment 100 of FIG. 1 includes a hub device 180 that iscommunicatively coupled to the network(s) 162 directly or via thenetwork interface 160. The hub device 180 is further communicativelycoupled to one or more of the above intelligent, multi-sensing,network-connected devices (e.g., smart devices of the smart homeenvironment 100). Each of these smart devices optionally communicateswith the hub device 180 using one or more radio communication networksavailable at least in the smart home environment 100 (e.g., ZigBee,Z-Wave, Insteon, Bluetooth, Wi-Fi and other radio communicationnetworks). In some implementations, the hub device 180 and devicescoupled with/to the hub device can be controlled and/or interacted withvia an application running on a smart phone, household controller,laptop, tablet computer, game console or similar electronic device. Insome implementations, a user of such controller application can viewstatus of the hub device or coupled smart devices, configure the hubdevice to interoperate with smart devices newly introduced to the homenetwork, commission new smart devices, and adjust or view settings ofconnected smart devices, etc. In some implementations the hub deviceextends capabilities of low capability smart device to matchcapabilities of the highly capable smart devices of the same type,integrates functionality of multiple different device types—even acrossdifferent communication protocols, and is configured to streamlineadding of new devices and commissioning of the hub device.

FIG. 2 is a block diagram illustrating an example network architecture200 that includes a smart home network 202 in accordance with someimplementations. In some implementations, the smart devices 204 in thesmart home environment 100 (e.g., devices 102, 104, 106, 108, 110, 112,114, 116, 118, 120, and/or 122) combine with the hub device 180 tocreate a mesh network in smart home network 202. In someimplementations, one or more smart devices 204 in the smart home network202 operate as a smart home controller. Additionally and/oralternatively, hub device 180 operates as the smart home controller. Insome implementations, a smart home controller has more computing powerthan other smart devices. In some implementations, a smart homecontroller processes inputs (e.g., from smart devices 204, electronicdevice 166, and/or smart home provider server system 164) and sendscommands (e.g., to smart devices 204 in the smart home network 202) tocontrol operation of the smart home environment 100. In someimplementations, some of the smart devices 204 in the smart home network202 (e.g., in the mesh network) are “spokesman” nodes (e.g., 204-1) andothers are “low-powered” nodes (e.g., 204-9). Some of the smart devicesin the smart home environment 100 are battery powered, while others havea regular and reliable power source, such as by connecting to wiring(e.g., to 120V line voltage wires) behind the walls 154 of the smarthome environment. The smart devices that have a regular and reliablepower source are referred to as “spokesman” nodes. These nodes aretypically equipped with the capability of using a wireless protocol tofacilitate bidirectional communication with a variety of other devicesin the smart home environment 100, as well as with the smart homeprovider server system 164. In some implementations, one or more“spokesman” nodes operate as a smart home controller. On the other hand,the devices that are battery powered are the “low-power” nodes. Thesenodes tend to be smaller than spokesman nodes and typically onlycommunicate using wireless protocols that require very little power,such as Zigbee, 6LoWPAN, etc.

In some implementations, some low-power nodes are incapable ofbidirectional communication. These low-power nodes send messages, butthey are unable to “listen”. Thus, other devices in the smart homeenvironment 100, such as the spokesman nodes, cannot send information tothese low-power nodes.

In some implementations, some low-power nodes are capable of only alimited bidirectional communication. For example, other devices are ableto communicate with the low-power nodes only during a certain timeperiod.

As described, in some implementations, the smart devices serve aslow-power and spokesman nodes to create a mesh network in the smart homeenvironment 100. In some implementations, individual low-power nodes inthe smart home environment regularly send out messages regarding whatthey are sensing, and the other low-powered nodes in the smart homeenvironment—in addition to sending out their own messages—forward themessages, thereby causing the messages to travel from node to node(i.e., device to device) throughout the smart home network 202. In someimplementations, the spokesman nodes in the smart home network 202,which are able to communicate using a relatively high-powercommunication protocol, such as IEEE 802.11, are able to switch to arelatively low-power communication protocol, such as IEEE 802.15.4, toreceive these messages, translate the messages to other communicationprotocols, and send the translated messages to other spokesman nodesand/or the smart home provider server system 164 (using, e.g., therelatively high-power communication protocol). Thus, the low-powerednodes using low-power communication protocols are able to send and/orreceive messages across the entire smart home network 202, as well asover the Internet 162 to the smart home provider server system 164. Insome implementations, the mesh network enables the smart home providerserver system 164 to regularly receive data from most or all of thesmart devices in the home, make inferences based on the data, facilitatestate synchronization across devices within and outside of the smarthome network 202, and send commands to one or more of the smart devicesto perform tasks in the smart home environment.

As described, the spokesman nodes and some of the low-powered nodes arecapable of “listening.” Accordingly, users, other devices, and/or thesmart home provider server system 164 may communicate control commandsto the low-powered nodes. For example, a user may use the electronicdevice 166 (e.g., a smart phone) to send commands over the Internet tothe smart home provider server system 164, which then relays thecommands to one or more spokesman nodes in the smart home network 202.The spokesman nodes may use a low-power protocol to communicate thecommands to the low-power nodes throughout the smart home network 202,as well as to other spokesman nodes that did not receive the commandsdirectly from the smart home provider server system 164.

In some implementations, a smart nightlight 170 (FIG. 1), which is anexample of a smart device 204, is a low-power node. In addition tohousing a light source, the smart nightlight 170 houses an occupancysensor, such as an ultrasonic or passive IR sensor, and an ambient lightsensor, such as a photo resistor or a single-pixel sensor that measureslight in the room. In some implementations, the smart nightlight 170 isconfigured to activate the light source when its ambient light sensordetects that the room is dark and when its occupancy sensor detects thatsomeone is in the room. In other implementations, the smart nightlight170 is simply configured to activate the light source when its ambientlight sensor detects that the room is dark. Further, in someimplementations, the smart nightlight 170 includes a low-power wirelesscommunication chip (e.g., a ZigBee chip) that regularly sends outmessages regarding the occupancy of the room and the amount of light inthe room, including instantaneous messages coincident with the occupancysensor detecting the presence of a person in the room. As mentionedabove, these messages may be sent wirelessly (e.g., using the meshnetwork) from node to node (i.e., smart device to smart device) withinthe smart home network 202 as well as over the Internet 162 to the smarthome provider server system 164.

Other examples of low-power nodes include battery-operated versions ofthe smart hazard detectors 104. These smart hazard detectors 104 areoften located in an area without access to constant and reliable powerand may include any number and type of sensors, such as smoke/fire/heatsensors (e.g., thermal radiation sensors), carbon monoxide/dioxidesensors, occupancy/motion sensors, ambient light sensors, ambienttemperature sensors, humidity sensors, and the like. Furthermore, smarthazard detectors 104 may send messages that correspond to each of therespective sensors to the other devices and/or the smart home providerserver system 164, such as by using the mesh network as described above.

Examples of spokesman nodes include smart doorbells 106, smartthermostats 102, smart wall switches 108, and smart wall plugs 110.These devices are often located near and connected to a reliable powersource, and therefore may include more power-consuming components, suchas one or more communication chips capable of bidirectionalcommunication in a variety of protocols.

In some implementations, the smart home environment 100 includes servicerobots 168 (FIG. 1) that are configured to carry out, in an autonomousmanner, any of a variety of household tasks.

As explained above with reference to FIG. 1, in some implementations,the smart home environment 100 of FIG. 1 includes a hub device 180 thatis communicatively coupled to the network(s) 162 directly or via thenetwork interface 160. The hub device 180 is further communicativelycoupled to one or more of the smart devices using a radio communicationnetwork that is available at least in the smart home environment 100.Communication protocols used by the radio communication network include,but are not limited to, ZigBee, Z-Wave, Insteon, EuOcean, Thread, OSIAN,Bluetooth Low Energy and the like. In some implementations, the hubdevice 180 not only converts the data received from each smart device tomeet the data format requirements of the network interface 160 or thenetwork(s) 162, but also converts information received from the networkinterface 160 or the network(s) 162 to meet the data format requirementsof the respective communication protocol associated with a targetedsmart device. In some implementations, in addition to data formatconversion, the hub device 180 further processes the data received fromthe smart devices or information received from the network interface 160or the network(s) 162 preliminary. For example, the hub device 180 canintegrate inputs from multiple sensors/connected devices (includingsensors/devices of the same and/or different types), perform higherlevel processing on those inputs—e.g., to assess the overall environmentand coordinate operation among the different sensors/devices—and/orprovide instructions to the different devices based on the collection ofinputs and programmed processing. It is also noted that in someimplementations, the network interface 160 and the hub device 180 areintegrated to one network device. Functionality described herein isrepresentative of particular implementations of smart devices, controlapplication(s) running on representative electronic device(s) (such as asmart phone), hub device(s) 180, and server(s) coupled to hub device(s)via the Internet or other Wide Area Network. All or a portion of thisfunctionality and associated operations can be performed by any elementsof the described system—for example, all or a portion of thefunctionality described herein as being performed by an implementationof the hub device can be performed, in different system implementations,in whole or in part on the server, one or more connected smart devicesand/or the control application, or different combinations thereof.

FIG. 3 illustrates a network-level view of an extensible devices andservices platform with which the smart home environment of FIG. 1 isintegrated, in accordance with some implementations. The extensibledevices and services platform 300 includes smart home provider serversystem 164. Each of the intelligent, network-connected devices describedwith reference to FIG. 1 (e.g., 102, 104, 106, 108, 110, 112, 114, 116and 118, identified simply as “devices” in FIGS. 2-4) may communicatewith the smart home provider server system 164. For example, aconnection to the Internet 162 may be established either directly (forexample, using 3G/4G connectivity to a wireless carrier), or through anetwork interface 160 (e.g., a router, switch, gateway, hub device, oran intelligent, dedicated whole-home controller node), or through anycombination thereof.

In some implementations, the devices and services platform 300communicates with and collects data from the smart devices of the smarthome environment 100. In addition, in some implementations, the devicesand services platform 300 communicates with and collects data from aplurality of smart home environments across the world. For example, thesmart home provider server system 164 collects home data 302 from thedevices of one or more smart home environments 100, where the devicesmay routinely transmit home data or may transmit home data in specificinstances (e.g., when a device queries the home data 302). Examplecollected home data 302 includes, without limitation, power consumptiondata, blackbody radiation data, occupancy data, HVAC settings and usagedata, carbon monoxide levels data, carbon dioxide levels data, volatileorganic compounds levels data, sleeping schedule data, cooking scheduledata, inside and outside temperature humidity data, televisionviewership data, inside and outside noise level data, pressure data,video data, etc.

In some implementations, the smart home provider server system 164provides one or more services 304 to smart homes and/or third parties.Example services 304 include, without limitation, software updates,customer support, sensor data collection/logging, remote access, remoteor distributed control, and/or use suggestions (e.g., based on collectedhome data 302) to improve performance, reduce utility cost, increasesafety, etc. In some implementations, data associated with the services304 is stored at the smart home provider server system 164, and thesmart home provider server system 164 retrieves and transmits the dataat appropriate times (e.g., at regular intervals, upon receiving arequest from a user, etc.).

In some implementations, the extensible devices and services platform300 includes a processing engine 306, which may be concentrated at asingle server or distributed among several different computing entitieswithout limitation. In some implementations, the processing engine 306includes engines configured to receive data from the devices of smarthome environments 100 (e.g., via the Internet 162 and/or a networkinterface 160), to index the data, to analyze the data and/or togenerate statistics based on the analysis or as part of the analysis. Insome implementations, the analyzed data is stored as derived home data308.

Results of the analysis or statistics may thereafter be transmitted backto the device that provided home data used to derive the results, toother devices, to a server providing a webpage to a user of the device,or to other non-smart device entities. In some implementations, usagestatistics, usage statistics relative to use of other devices, usagepatterns, and/or statistics summarizing sensor readings are generated bythe processing engine 306 and transmitted. The results or statistics maybe provided via the Internet 162. In this manner, the processing engine306 may be configured and programmed to derive a variety of usefulinformation from the home data 302. A single server may include one ormore processing engines.

The derived home data 308 may be used at different granularities for avariety of useful purposes, ranging from explicit programmed control ofthe devices on a per-home, per-neighborhood, or per-region basis (forexample, demand-response programs for electrical utilities), to thegeneration of inferential abstractions that may assist on a per-homebasis (for example, an inference may be drawn that the homeowner hasleft for vacation and so security detection equipment may be put onheightened sensitivity), to the generation of statistics and associatedinferential abstractions that may be used for government or charitablepurposes. For example, processing engine 306 may generate statisticsabout device usage across a population of devices and send thestatistics to device users, service providers or other entities (e.g.,entities that have requested the statistics and/or entities that haveprovided monetary compensation for the statistics).

In some implementations, to encourage innovation and research and toincrease products and services available to users, the devices andservices platform 300 exposes a range of application programminginterfaces (APIs) 310 to third parties, such as charities 314,governmental entities 316 (e.g., the Food and Drug Administration or theEnvironmental Protection Agency), academic institutions 318 (e.g.,university researchers), businesses 320 (e.g., providing devicewarranties or service to related equipment, targeting advertisementsbased on home data), utility companies 324, and other third parties. TheAPIs 310 are coupled to and permit third-party systems to communicatewith the smart home provider server system 164, including the services304, the processing engine 306, the home data 302, and the derived homedata 308. In some implementations, the APIs 310 allow applicationsexecuted by the third parties to initiate specific data processing tasksthat are executed by the smart home provider server system 164, as wellas to receive dynamic updates to the home data 302 and the derived homedata 308.

For example, third parties may develop programs and/or applications(e.g., web applications or mobile applications) that integrate with thesmart home provider server system 164 to provide services andinformation to users. Such programs and applications may be, forexample, designed to help users reduce energy consumption, topreemptively service faulty equipment, to prepare for high servicedemands, to track past service performance, etc., and/or to performother beneficial functions or tasks.

FIG. 4 illustrates an abstracted functional view 400 of the extensibledevices and services platform 300 of FIG. 3, with reference to aprocessing engine 306 as well as devices of the smart home environment,in accordance with some implementations. Even though devices situated insmart home environments will have a wide variety of different individualcapabilities and limitations, the devices may be thought of as sharingcommon characteristics in that each device is a data consumer 402 (DC),a data source 404 (DS), a services consumer 406 (SC), and a servicessource 408 (SS). Advantageously, in addition to providing controlinformation used by the devices to achieve their local and immediateobjectives, the extensible devices and services platform 300 may also beconfigured to use the large amount of data that is generated by thesedevices. In addition to enhancing or optimizing the actual operation ofthe devices themselves with respect to their immediate functions, theextensible devices and services platform 300 may be directed to“repurpose” that data in a variety of automated, extensible, flexible,and/or scalable ways to achieve a variety of useful objectives. Theseobjectives may be predefined or adaptively identified based on, e.g.,usage patterns, device efficiency, and/or user input (e.g., requestingspecific functionality).

FIG. 4 shows processing engine 306 as including a number of processingparadigms 410. In some implementations, processing engine 306 includes amanaged services paradigm 410 a that monitors and manages primary orsecondary device functions. The device functions may include ensuringproper operation of a device given user inputs, estimating that (e.g.,and responding to an instance in which) an intruder is or is attemptingto be in a dwelling, detecting a failure of equipment coupled to thedevice (e.g., a light bulb having burned out), implementing or otherwiseresponding to energy demand response events, providing a heat-sourcealert, and/or alerting a user of a current or predicted future event orcharacteristic. In some implementations, processing engine 306 includesan advertising/communication paradigm 410 b that estimatescharacteristics (e.g., demographic information), desires and/or productsof interest of a user based on device usage. Services, promotions,products or upgrades may then be offered or automatically provided tothe user. In some implementations, processing engine 306 includes asocial paradigm 410 c that uses information from a social network,provides information to a social network (for example, based on deviceusage), and/or processes data associated with user and/or deviceinteractions with the social network platform. For example, a user'sstatus as reported to their trusted contacts on the social network maybe updated to indicate when the user is home based on light detection,security system inactivation or device usage detectors. As anotherexample, a user may be able to share device-usage statistics with otherusers. In yet another example, a user may share HVAC settings thatresult in low power bills and other users may download the HVAC settingsto their smart thermostat 102 to reduce their power bills.

In some implementations, processing engine 306 includes achallenges/rules/compliance/rewards paradigm 410 d that informs a userof challenges, competitions, rules, compliance regulations and/orrewards and/or that uses operation data to determine whether a challengehas been met, a rule or regulation has been complied with and/or areward has been earned. The challenges, rules, and/or regulations mayrelate to efforts to conserve energy, to live safely (e.g., reducing theoccurrence of heat-source alerts) (e.g., reducing exposure to toxins orcarcinogens), to conserve money and/or equipment life, to improvehealth, etc. For example, one challenge may involve participants turningdown their thermostat by one degree for one week. Those participantsthat successfully complete the challenge are rewarded, such as withcoupons, virtual currency, status, etc. Regarding compliance, an exampleinvolves a rental-property owner making a rule that no renters arepermitted to access certain owner's rooms. The devices in the roomhaving occupancy sensors may send updates to the owner when the room isaccessed.

In some implementations, processing engine 306 integrates or otherwiseuses extrinsic information 412 from extrinsic sources to improve thefunctioning of one or more processing paradigms. Extrinsic information412 may be used to interpret data received from a device, to determine acharacteristic of the environment near the device (e.g., outside astructure that the device is enclosed in), to determine services orproducts available to the user, to identify a social network orsocial-network information, to determine contact information of entities(e.g., public-service entities such as an emergency-response team, thepolice or a hospital) near the device, to identify statistical orenvironmental conditions, trends or other information associated with ahome or neighborhood, and so forth.

FIG. 5 illustrates a representative operating environment 500 in which ahub device server system 508 provides data processing for monitoring andfacilitating review of motion events in video streams captured by videocameras 118. As shown in FIG. 5, the hub device server system 508receives video data from video sources 522 (including cameras 118)located at various physical locations (e.g., inside homes, restaurants,stores, streets, parking lots, and/or the smart home environments 100 ofFIG. 1). Each video source 522 may be bound to one or more revieweraccounts, and the hub device server system 508 provides video monitoringdata for the video source 522 to client devices 504 associated with thereviewer accounts. For example, the portable electronic device 166 is anexample of the client device 504.

In some implementations, the smart home provider server system 164 or acomponent thereof serves as the hub device server system 508. In someimplementations, the hub device server system 508 is a dedicated videoprocessing server that provides video processing services to videosources and client devices 504 independent of other services provided bythe hub device server system 508.

In some implementations, each of the video sources 522 includes one ormore video cameras 118 that capture video and send the captured video tothe hub device server system 508 substantially in real-time. In someimplementations, each of the video sources 522 optionally includes acontroller device (not shown) that serves as an intermediary between theone or more cameras 118 and the hub device server system 508. Thecontroller device receives the video data from the one or more cameras118, optionally, performs some preliminary processing on the video data,and sends the video data to the hub device server system 508 on behalfof the one or more cameras 118 substantially in real-time. In someimplementations, each camera has its own on-board processingcapabilities to perform some preliminary processing on the capturedvideo data before sending the processed video data (along with metadataobtained through the preliminary processing) to the controller deviceand/or the hub device server system 508.

As shown in FIG. 5, in accordance with some implementations, each of theclient devices 504 includes a client-side module 502. The client-sidemodule 502 communicates with a server-side module 506 executed on thehub device server system 508 through the one or more networks 162. Theclient-side module 502 provides client-side functionalities for theevent monitoring and review processing and communications with theserver-side module 506. The server-side module 506 provides server-sidefunctionalities for event monitoring and review processing for anynumber of client-side modules 502 each residing on a respective clientdevice 504. The server-side module 506 also provides server-sidefunctionalities for video processing and camera control for any numberof the video sources 522, including any number of control devices andthe cameras 118.

In some implementations, the server-side module 506 includes one or moreprocessors 512, a video storage database 514, device and accountdatabases 516, an I/O interface to one or more client devices 518, andan I/O interface to one or more video sources 520. The I/O interface toone or more clients 518 facilitates the client-facing input and outputprocessing for the server-side module 506. The databases 516 store aplurality of profiles for reviewer accounts registered with the videoprocessing server, where a respective user profile includes accountcredentials for a respective reviewer account, and one or more videosources linked to the respective reviewer account. The I/O interface toone or more video sources 520 facilitates communications with one ormore video sources 522 (e.g., groups of one or more cameras 118 andassociated controller devices). The video storage database 514 storesraw video data received from the video sources 522, as well as varioustypes of metadata, such as motion events, event categories, eventcategory models, event filters, and event masks, for use in dataprocessing for event monitoring and review for each reviewer account.

Examples of a representative client device 504 include, but are notlimited to, a handheld computer, a wearable computing device, a personaldigital assistant (PDA), a tablet computer, a laptop computer, a desktopcomputer, a cellular telephone, a smart phone, an enhanced generalpacket radio service (EGPRS) mobile phone, a media player, a navigationdevice, a game console, a television, a remote control, a point-of-sale(POS) terminal, vehicle-mounted computer, an ebook reader, or acombination of any two or more of these data processing devices or otherdata processing devices.

Examples of the one or more networks 162 include local area networks(LAN) and wide area networks (WAN) such as the Internet. The one or morenetworks 162 are, optionally, implemented using any known networkprotocol, including various wired or wireless protocols, such asEthernet, Universal Serial Bus (USB), FIREWIRE, Long Term Evolution(LTE), Global System for Mobile Communications (GSM), Enhanced Data GSMEnvironment (EDGE), code division multiple access (CDMA), time divisionmultiple access (TDMA), Bluetooth, Wi-Fi, voice over Internet Protocol(VoIP), Wi-MAX, or any other suitable communication protocol.

In some implementations, the hub device server system 508 is implementedon one or more standalone data processing apparatuses or a distributednetwork of computers. In some implementations, the hub device serversystem 508 also employs various virtual devices and/or services of thirdparty service providers (e.g., third-party cloud service providers) toprovide the underlying computing resources and/or infrastructureresources of the hub device server system 508. In some implementations,the hub device server system 508 includes, but is not limited to, ahandheld computer, a tablet computer, a laptop computer, a desktopcomputer, or a combination of any two or more of these data processingdevices or other data processing devices.

The server-client environment 500 shown in FIG. 1 includes both aclient-side portion (e.g., the client-side module 502) and a server-sideportion (e.g., the server-side module 506). The division offunctionalities between the client and server portions of operatingenvironment 500 can vary in different implementations. Similarly, thedivision of functionalities between the video source 522 and the hubdevice server system 508 can vary in different implementations. Forexample, in some implementations, client-side module 502 is athin-client that provides only user-facing input and output processingfunctions, and delegates all other data processing functionalities to abackend server (e.g., the hub device server system 508). Similarly, insome implementations, a respective one of the video sources 522 is asimple video capturing device that continuously captures and streamsvideo data to the hub device server system 508 without no or limitedlocal preliminary processing on the video data. Although many aspects ofthe present technology are described from the perspective of the hubdevice server system 508, the corresponding actions performed by theclient device 504 and/or the video sources 522 would be apparent to onesskilled in the art without any creative efforts. Similarly, some aspectsof the present technology may be described from the perspective of theclient device or the video source, and the corresponding actionsperformed by the video server would be apparent to ones skilled in theart without any creative efforts. Furthermore, some aspects of thepresent technology may be performed by the hub device server system 508,the client device 504, and the video sources 522 cooperatively.

It should be understood that operating environment 500 that involves thehub device server system 508, the video sources 522 and the videocameras 118 is merely an example. Many aspects of operating environment500 are generally applicable in other operating environments in which aserver system provides data processing for monitoring and facilitatingreview of data captured by other types of electronic devices (e.g.,smart thermostats 102, smart hazard detectors 104, smart doorbells 106,smart wall plugs 110, appliances 112 and the like).

The electronic devices, the client devices or the server systemcommunicate with each other using the one or more communication networks162. In an example smart home environment, two or more devices (e.g.,the network interface device 160, the hub device 180, and the clientdevices 504-m) are located in close proximity to each other, such thatthey could be communicatively coupled in the same sub-network 162A viawired connections, a WLAN or a Bluetooth Personal Area Network (PAN).The Bluetooth PAN is optionally established based on classical Bluetoothtechnology or Bluetooth Low Energy (BLE) technology. This smart homeenvironment further includes one or more other radio communicationnetworks 162B through which at least some of the electronic devices ofthe video sources 522-n exchange data with the hub device 180.Alternatively, in some situations, some of the electronic devices of thevideo sources 522-n communicate with the network interface device 160directly via the same sub-network 162A that couples devices 160, 180 and504-m. In some implementations (e.g., in the network 162C), both theclient device 504-m and the electronic devices of the video sources522-n communicate directly via the network(s) 162 without passing thenetwork interface device 160 or the hub device 180.

In some implementations, during normal operation, the network interfacedevice 160 and the hub device 180 communicate with each other to form anetwork gateway through which data are exchanged with the electronicdevice of the video sources 522-n. As explained above, the networkinterface device 160 and the hub device 180 optionally communicate witheach other via a sub-network 162A.

FIG. 6 is a block diagram illustrating a representative hub device 180in accordance with some implementations. In some implementations, thehub device 180 includes one or more processing units (e.g., CPUs, ASICs,FPGAs, microprocessors, and the like) 602, one or more communicationinterfaces 604, memory 606, radios 640, and one or more communicationbuses 608 for interconnecting these components (sometimes called achipset). In some implementations, the hub device 180 includes one ormore input devices 610 such as one or more buttons for receiving input.In some implementations, the hub device 180 includes one or more outputdevices 612 such as one or more indicator lights, a sound card, aspeaker, a small display for displaying textual information and errorcodes, etc. Furthermore, in some implementations, the hub device 180uses a microphone and voice recognition or a camera and gesturerecognition to supplement or replace the keyboard. In someimplementations, the hub device 180 includes a location detection device614, such as a GPS (global positioning satellite) or other geo-locationreceiver, for determining the location of the hub device 180.

The hub device 180 optionally includes one or more built-in sensors (notshown), including, for example, one or more thermal radiation sensors,ambient temperature sensors, humidity sensors, IR sensors, occupancysensors (e.g., using RFID sensors), ambient light sensors, motiondetectors, accelerometers, and/or gyroscopes.

The radios 640 enables one or more radio communication networks in thesmart home environments, and allows a hub device to communicate withsmart devices. In some implementations, the radios 640 are capable ofdata communications using any of a variety of custom or standardwireless protocols (e.g., IEEE 802.15.4, Wi-Fi, ZigBee, 6LoWPAN, Thread,Z-Wave, Bluetooth Smart, ISA100.11a, WirelessHART, MiWi, etc.) custom orstandard wired protocols (e.g., Ethernet, HomePlug, etc.), and/or anyother suitable communication protocol, including communication protocolsnot yet developed as of the filing date of this document.

Communication interfaces 604 include, for example, hardware capable ofdata communications using any of a variety of custom or standardwireless protocols (e.g., IEEE 802.15.4, Wi-Fi, ZigBee, 6LoWPAN, Thread,Z-Wave, Bluetooth Smart, ISA100.11a, WirelessHART, MiWi, etc.) and/orany of a variety of custom or standard wired protocols (e.g., Ethernet,HomePlug, etc.), or any other suitable communication protocol, includingcommunication protocols not yet developed as of the filing date of thisdocument.

Memory 606 includes high-speed random access memory, such as DRAM, SRAM,DDR RAM, or other random access solid state memory devices; and,optionally, includes non-volatile memory, such as one or more magneticdisk storage devices, one or more optical disk storage devices, one ormore flash memory devices, or one or more other non-volatile solid statestorage devices. Memory 606, or alternatively the non-volatile memorywithin memory 606, includes a non-transitory computer readable storagemedium. In some implementations, memory 606, or the non-transitorycomputer readable storage medium of memory 606, stores the followingprograms, modules, and data structures, or a subset or superset thereof:

-   -   Operating logic 616 including procedures for handling various        basic system services and for performing hardware dependent        tasks;    -   Hub device communication module 618 for connecting to and        communicating with other network devices (e.g., network        interface 160, such as a router that provides Internet        connectivity, networked storage devices, network routing        devices, server system 508, etc.) connected to one or more        networks 162 via one or more communication interfaces 604 (wired        or wireless);    -   Radio communication module 620 for connecting the hub device 180        to other devices (e.g., controller devices, smart devices 204 in        smart home environment 100, client devices 504) via one or more        radio communication devices (e.g., radios 640);    -   User interface module 622 for providing and displaying a user        interface in which settings, captured data, and/or other data        for one or more devices (e.g., smart devices 204 in smart home        environment 100) can be configured and/or viewed, for displaying        notifications of trigger events (e.g., the GUI and notification        1300 of FIG. 13A), and/or for detecting user inputs (e.g., user        input indicating selection of a UI element, such as an override        input); and    -   Hub device database 624, including but not limited to:        -   Sensor information 6240 for storing and managing data            received, detected, and/or transmitted by one or more            sensors of the hub device 180 and/or one or more other            devices (e.g., smart devices 204 in smart home environment            100);        -   Device settings 6242 for storing operational settings for            one or more devices (e.g., coupled smart devices 204 in            smart home environment 100); and        -   Communication protocol information 6244 for storing and            managing protocol information for one or more protocols            (e.g., standard wireless protocols, such as ZigBee, Z-Wave,            etc., and/or custom or standard wired protocols, such as            Ethernet); and    -   Trigger detection module 626 for detecting trigger events (e.g.,        using optional built-in sensors and inputs of the hub device        180, smart devices 204, and/or any other devices connected to        the network 162) and providing notifications of detected trigger        events;    -   Lock device state module 628 for determining a target state and        current state of a lock device (e.g., smart door lock 120, FIG.        11), and for providing instructions to the lock device (e.g., if        the target state and current state of the lock device are not        the same);    -   Security profile module 630 for managing and storing respective        user security profiles and settings (e.g., FIG. 13C); and    -   Adjustment rule module 632 for creating and storing adjustment        rules based on user inputs (e.g., override inputs), where in        some implementations, a target state of a lock device is based        on one or more created adjustment rules (e.g., used by lock        device state module 628).

Each of the above identified elements (e.g., modules stored in memory206 of hub device 180) may be stored in one or more of the previouslymentioned memory devices (e.g., the memory of any of the smart devicesin smart home environment 100, FIG. 1), and corresponds to a set ofinstructions for performing a function described above. The aboveidentified modules or programs (i.e., sets of instructions) need not beimplemented as separate software programs, procedures, or modules, andthus various subsets of these modules may be combined or otherwisere-arranged in various implementations. In some implementations, memory606, optionally, stores a subset of the modules and data structuresidentified above. Furthermore, memory 606, optionally, stores additionalmodules and data structures not described above.

FIG. 7 is a block diagram illustrating the hub server system 508 inaccordance with some implementations. The hub server system 508,typically, includes one or more processing units (CPUs) 702, one or morenetwork interfaces 704 (e.g., including an I/O interface to one or moreclient devices and an I/O interface to one or more electronic devices),memory 706, and one or more communication buses 708 for interconnectingthese components (sometimes called a chipset). Memory 706 includeshigh-speed random access memory, such as DRAM, SRAM, DDR RAM, or otherrandom access solid state memory devices; and, optionally, includesnon-volatile memory, such as one or more magnetic disk storage devices,one or more optical disk storage devices, one or more flash memorydevices, or one or more other non-volatile solid state storage devices.Memory 706, optionally, includes one or more storage devices remotelylocated from one or more processing units 702. Memory 706, oralternatively the non-volatile memory within memory 706, includes anon-transitory computer readable storage medium. In someimplementations, memory 706, or the non-transitory computer readablestorage medium of memory 706, stores the following programs, modules,and data structures, or a subset or superset thereof:

-   -   Operating system 710 including procedures for handling various        basic system services and for performing hardware dependent        tasks;    -   Network communication module 712 for connecting the hub server        system 508 to other systems and devices (e.g., client devices,        electronic devices, and systems connected to one or more        networks 162, FIGS. 1-5) via one or more network interfaces 704        (wired or wireless);    -   Server-side module 714, which provides server-side        functionalities for device control, data processing and data        review, including but not limited to:        -   Data receiving module 7140 for receiving data from            electronic devices (e.g., video data from a camera 118,            FIG. 1) via the hub device 180, and preparing the received            data for further processing and storage in the data storage            database 7160;        -   Hub and device control module 7142 for generating and            sending server-initiated control commands to modify            operation modes of electronic devices (e.g., devices of a            smart home environment 100), and/or receiving (e.g., from            client devices 504) and forwarding user-initiated control            commands to modify operation modes of the electronic            devices;        -   Data processing module 7144 for processing the data provided            by the electronic devices, and/or preparing and sending            processed data to a device for review (e.g., client devices            504 for review by a user);        -   Trigger detection module 7146 for detecting trigger events            (e.g., using optional built-in sensors and inputs of the hub            device 180, smart devices 204, and/or any other devices            connected to the network 162) and providing notifications of            detected trigger events;        -   Lock device state module 7148 for determining a target state            and current state of a lock device (e.g., smart door lock            120, FIG. 11), and for providing instructions to the lock            device (e.g., if the target state and current state of the            lock device are not the same);        -   Security profile module 7150 for managing and storing            respective user security profiles and settings (e.g., FIG.            13C); and        -   Adjustment rule module 7152 for creating and storing            adjustment rules based on user inputs (e.g., override            inputs), where in some implementations, a target state of a            lock device is based on one or more created adjustment rules            (e.g., used by lock device state module 628); and    -   Server database 716, including but not limited to:        -   Data storage database 7160 for storing data associated with            each electronic device (e.g., each camera) of each user            account, as well as data processing models, processed data            results, and other relevant metadata (e.g., names of data            results, location of electronic device, creation time,            duration, settings of the electronic device, etc.)            associated with the data, wherein (optionally) all or a            portion of the data and/or processing associated with the            hub device 180 or smart devices are stored securely;        -   Account database 7162 for storing account information for            user accounts, including user account information,            information and settings for linked hub devices and            electronic devices (e.g., hub device identifications), hub            device specific secrets, relevant user and hardware            characteristics (e.g., service tier, device model, storage            capacity, processing capabilities, etc.), user interface            settings, data review preferences, etc., where the            information for associated electronic devices includes, but            is not limited to, one or more device identifiers (e.g., MAC            address and UUID), device specific secrets, and displayed            titles; and        -   Device Information Database 7164 for storing device            information related to one or more hub devices, e.g., device            identifiers and hub device specific secrets, independently            of whether the corresponding hub devices have been            associated with any user account.

Each of the above identified elements may be stored in one or more ofthe previously mentioned memory devices, and corresponds to a set ofinstructions for performing a function described above. The aboveidentified modules or programs (i.e., sets of instructions) need not beimplemented as separate software programs, procedures, or modules, andthus various subsets of these modules may be combined or otherwisere-arranged in various implementations. In some implementations, memory706, optionally, stores a subset of the modules and data structuresidentified above. Furthermore, memory 706, optionally, stores additionalmodules and data structures not described above.

FIG. 8 is a block diagram illustrating a representative client device504 associated with a user account in accordance with someimplementations. The client device 504, typically, includes one or moreprocessing units (CPUs) 802, one or more network interfaces 804, memory806, and one or more communication buses 808 for interconnecting thesecomponents (sometimes called a chipset). Optionally, the client devicealso includes a user interface 810 and one or more built-in sensors 890(e.g., accelerometer and gyroscope). User interface 810 includes one ormore output devices 812 that enable presentation of media content,including one or more speakers and/or one or more visual displays. Userinterface 810 also includes one or more input devices 814, includinguser interface components that facilitate user input such as a keyboard,a mouse, a voice-command input unit or microphone, a touch screendisplay, a touch-sensitive input pad, a gesture capturing camera, orother input buttons or controls. Furthermore, some the client devicesuse a microphone and voice recognition or a camera and gesturerecognition to supplement or replace the keyboard. In someimplementations, the client device includes one or more cameras,scanners, or photo sensor units for capturing images (not shown).Optionally, the client device includes a location detection device 816,such as a GPS (global positioning satellite) or other geo-locationreceiver, for determining the location of the client device.

Memory 806 includes high-speed random access memory, such as DRAM, SRAM,DDR RAM, or other random access solid state memory devices; and,optionally, includes non-volatile memory, such as one or more magneticdisk storage devices, one or more optical disk storage devices, one ormore flash memory devices, or one or more other non-volatile solid statestorage devices. Memory 806, optionally, includes one or more storagedevices remotely located from one or more processing units 802. Memory806, or alternatively the non-volatile memory within memory 806,includes a non-transitory computer readable storage medium. In someimplementations, memory 806, or the non-transitory computer readablestorage medium of memory 806, stores the following programs, modules,and data structures, or a subset or superset thereof:

-   -   Operating system 818 including procedures for handling various        basic system services and for performing hardware dependent        tasks;    -   Network communication module 820 for connecting the client        device 504 to other systems and devices (e.g., client devices,        electronic devices, and systems connected to one or more        networks 162, FIGS. 1-5) via one or more network interfaces 804        (wired or wireless);    -   Input processing module 822 for detecting one or more user        inputs or interactions from one of the one or more input devices        814 and interpreting the detected input or interaction;    -   One or more applications 824 for execution by the client device        (e.g., games, social network applications, smart home        applications, and/or other web or non-web based applications)        for controlling devices (e.g., sending commands, configuring        settings, etc. to hub devices and/or other client or electronic        devices) and for reviewing data captured by the devices (e.g.,        device status and settings, captured data, or other information        regarding the hub device or other connected devices);    -   User interface module 622 for providing and displaying a user        interface in which settings, captured data, and/or other data        for one or more devices (e.g., smart devices 204 in smart home        environment 100) can be configured and/or viewed, for displaying        notifications of trigger events (e.g., the GUI and notification        1300 of FIG. 13A), and/or for detecting user inputs (e.g., user        input indicating selection of a UI element, such as an override        input);    -   Client-side module 828, which provides client-side        functionalities for device control, data processing and data        review, including but not limited to:        -   Hub device and device control module 8280 for generating            control commands for modifying an operating mode of the hub            device or the electronic devices in accordance with user            inputs; and        -   Data review module 8282 for providing user interfaces for            reviewing data processed by the hub server system 508; and    -   Client data 830 storing data associated with the user account        and electronic devices, including, but is not limited to:        -   Account data 8300 storing information related to both user            accounts loaded on the client device and electronic devices            (e.g., of the video sources 522) associated with the user            accounts, wherein such information includes cached login            credentials, hub device identifiers (e.g., MAC addresses and            UUIDs), electronic device identifiers (e.g., MAC addresses            and UUIDs), user interface settings, display preferences,            authentication tokens and tags, password keys, etc.; and        -   Local data storage database 8302 for selectively storing raw            or processed data associated with electronic devices (e.g.,            of the video sources 522, such as a camera 118); and    -   Trigger detection module 832 for detecting trigger events (e.g.,        using optional built-in sensors and inputs of the hub device        180, smart devices 204, and/or any other devices connected to        the network 162) and providing notifications of detected trigger        events;    -   Lock device state module 834 for determining a target state and        current state of a lock device (e.g., smart door lock 120, FIG.        11), and for providing instructions to the lock device (e.g., if        the target state and current state of the lock device are not        the same);    -   Security profile module 836 for managing and storing respective        user security profiles and settings (e.g., FIG. 13C); and    -   Adjustment rule module 838 for creating and storing adjustment        rules based on user inputs (e.g., override inputs), where in        some implementations, a target state of a lock device is based        on one or more created adjustment rules (e.g., used by lock        device state module 628).

Each of the above identified elements may be stored in one or more ofthe previously mentioned memory devices, and corresponds to a set ofinstructions for performing a function described above. The aboveidentified modules or programs (i.e., sets of instructions) need not beimplemented as separate software programs, procedures, modules or datastructures, and thus various subsets of these modules may be combined orotherwise re-arranged in various implementations. In someimplementations, memory 806, optionally, stores a subset of the modulesand data structures identified above. Furthermore, memory 806,optionally, stores additional modules and data structures not describedabove.

FIG. 9 is a block diagram illustrating a representative smart device 204in accordance with some implementations. In some implementations, thesmart device 204 (e.g., any devices of a smart home environment 100,FIGS. 1 and 2) includes one or more processing units (e.g., CPUs, ASICs,FPGAs, microprocessors, and the like) 902, one or more communicationinterfaces 904, memory 906, radios 940, and one or more communicationbuses 908 for interconnecting these components (sometimes called achipset). In some implementations, user interface 910 includes one ormore output devices 912 that enable presentation of media content,including one or more speakers and/or one or more visual displays. Insome implementations, user interface 910 also includes one or more inputdevices 914, including user interface components that facilitate userinput such as a keyboard, a mouse, a voice-command input unit ormicrophone, a touch screen display, a touch-sensitive input pad, agesture capturing camera, or other input buttons or controls.Furthermore, some smart devices 204 use a microphone and voicerecognition or a camera and gesture recognition to supplement or replacethe keyboard. In some implementations, the smart device 204 includes oneor more image/video capture devices 918 (e.g., cameras, video cameras,scanners, photo sensor units). Optionally, the client device includes alocation detection device 916, such as a GPS (global positioningsatellite) or other geo-location receiver, for determining the locationof the smart device 204.

The built-in sensors 990 include, for example, one or more thermalradiation sensors, ambient temperature sensors, humidity sensors, IRsensors, occupancy sensors (e.g., using RFID sensors), ambient lightsensors, motion detectors, accelerometers, and/or gyroscopes.

The radios 940 enable one or more radio communication networks in thesmart home environments, and allow a smart device 204 to communicatewith other devices. In some implementations, the radios 940 are capableof data communications using any of a variety of custom or standardwireless protocols (e.g., IEEE 802.15.4, Wi-Fi, ZigBee, 6LoWPAN, Thread,Z-Wave, Bluetooth Smart, ISA100.11a, WirelessHART, MiWi, etc.) custom orstandard wired protocols (e.g., Ethernet, HomePlug, etc.), and/or anyother suitable communication protocol, including communication protocolsnot yet developed as of the filing date of this document.

Communication interfaces 904 include, for example, hardware capable ofdata communications using any of a variety of custom or standardwireless protocols (e.g., IEEE 802.15.4, Wi-Fi, ZigBee, 6LoWPAN, Thread,Z-Wave, Bluetooth Smart, ISA100.11a, WirelessHART, MiWi, etc.) and/orany of a variety of custom or standard wired protocols (e.g., Ethernet,HomePlug, etc.), or any other suitable communication protocol, includingcommunication protocols not yet developed as of the filing date of thisdocument.

Memory 906 includes high-speed random access memory, such as DRAM, SRAM,DDR RAM, or other random access solid state memory devices; and,optionally, includes non-volatile memory, such as one or more magneticdisk storage devices, one or more optical disk storage devices, one ormore flash memory devices, or one or more other non-volatile solid statestorage devices. Memory 906, or alternatively the non-volatile memorywithin memory 906, includes a non-transitory computer readable storagemedium. In some implementations, memory 906, or the non-transitorycomputer readable storage medium of memory 906, stores the followingprograms, modules, and data structures, or a subset or superset thereof:

-   -   Operating logic 920 including procedures for handling various        basic system services and for performing hardware dependent        tasks;    -   Device communication module 922 for connecting to and        communicating with other network devices (e.g., network        interface 160, such as a router that provides Internet        connectivity, networked storage devices, network routing        devices, server system 508, etc.) connected to one or more        networks 162 via one or more communication interfaces 904 (wired        or wireless);    -   Radio Communication Module 924 for connecting the smart device        204 to other devices (e.g., controller devices, smart devices        204 in smart home environment 100, client devices 504) via one        or more radio communication devices (e.g., radios 940)    -   Input processing module 926 for detecting one or more user        inputs or interactions from the one or more input devices 914        and interpreting the detected inputs or interactions;    -   User interface module 928 for providing and displaying a user        interface in which settings, captured data, and/or other data        for one or more devices (e.g., the smart device 204, and/or        other devices in smart home environment 100) can be configured        and/or viewed, for displaying notifications of trigger events        (e.g., the GUI and notification 1300 of FIG. 13A), and/or for        detecting user inputs (e.g., user input indicating selection of        a UI element, such as an override input);    -   One or more applications 930 for execution by the smart device        930 (e.g., games, social network applications, smart home        applications, and/or other web or non-web based applications)        for controlling devices (e.g., executing commands, sending        commands, and/or configuring settings of the smart device 204        and/or other client/electronic devices), and for reviewing data        captured by devices (e.g., device status and settings, captured        data, or other information regarding the smart device 204 and/or        other client/electronic devices);    -   Device-side module 932, which provides device-side        functionalities for device control, data processing and data        review, including but not limited to:        -   Command receiving module 9320 for receiving, forwarding,            and/or executing instructions and control commands (e.g.,            from a client device 504, from a smart home provider server            system 164, from user inputs detected on the user interface            910, etc.) for operating the smart device 204;        -   Data processing module 9322 for processing data captured or            received by one or more inputs (e.g., input devices 914,            image/video capture devices 918, location detection device            916), sensors (e.g., built-in sensors 990), interfaces            (e.g., communication interfaces 904, radios 940), and/or            other components of the smart device 204, and for preparing            and sending processed data to a device for review (e.g.,            client devices 504 for review by a user); and    -   Device data 934 storing data associated with devices (e.g., the        smart device 204), including, but is not limited to:        -   Account data 9340 storing information related to user            accounts loaded on the smart device 204, wherein such            information includes cached login credentials, smart device            identifiers (e.g., MAC addresses and UUIDs), user interface            settings, display preferences, authentication tokens and            tags, password keys, etc.; and        -   Local data storage database 9342 for selectively storing raw            or processed data associated with the smart device 204            (e.g., video surveillance footage captured by a camera 118);            and    -   Trigger detection module 936 for detecting trigger events (e.g.,        using optional built-in sensors and inputs of the hub device        180, smart devices 204, and/or any other devices connected to        the network 162) and providing notifications of detected trigger        events;    -   Lock device state module 938 for determining a target state and        current state of a lock device (e.g., smart door lock 120, FIG.        11), and for providing instructions to the lock device (e.g., if        the target state and current state of the lock device are not        the same);    -   Security profile module 940 for managing and storing respective        user security profiles and settings (e.g., FIG. 13C); and    -   Adjustment rule module 942 for creating and storing adjustment        rules based on user inputs (e.g., override inputs), where in        some implementations, a target state of a lock device is based        on one or more created adjustment rules (e.g., used by lock        device state module 628).

Each of the above identified elements may be stored in one or more ofthe previously mentioned memory devices, and corresponds to a set ofinstructions for performing a function described above. The aboveidentified modules or programs (i.e., sets of instructions) need not beimplemented as separate software programs, procedures, or modules, andthus various subsets of these modules may be combined or otherwisere-arranged in various implementations. In some implementations, memory906, optionally, stores a subset of the modules and data structuresidentified above. Furthermore, memory 906, optionally, stores additionalmodules and data structures not described above.

FIG. 10 is a block diagram illustrating the smart home provider serversystem 164 in accordance with some implementations. The smart homeprovider server system 164, typically, includes one or more processingunits (CPUs) 1002, one or more network interfaces 1004 (e.g., includingan I/O interface to one or more client devices and an I/O interface toone or more electronic devices), memory 1006, and one or morecommunication buses 1008 for interconnecting these components (sometimescalled a chipset). Memory 1006 includes high-speed random access memory,such as DRAM, SRAM, DDR RAM, or other random access solid state memorydevices; and, optionally, includes non-volatile memory, such as one ormore magnetic disk storage devices, one or more optical disk storagedevices, one or more flash memory devices, or one or more othernon-volatile solid state storage devices. Memory 1006, optionally,includes one or more storage devices remotely located from one or moreprocessing units 1002. Memory 1006, or alternatively the non-volatilememory within memory 1006, includes a non-transitory computer readablestorage medium. In some implementations, memory 1006, or thenon-transitory computer readable storage medium of memory 1006, storesthe following programs, modules, and data structures, or a subset orsuperset thereof:

-   -   Operating system 1010 including procedures for handling various        basic system services and for performing hardware dependent        tasks;    -   Network communication module 1012 for connecting the smart home        provider server system 164 to other systems and devices (e.g.,        client devices, electronic devices, and systems connected to one        or more networks 162, FIGS. 1-5) via one or more network        interfaces 1004 (wired or wireless);    -   Server-side module 1014, which provides server-side        functionalities for device control, data processing and data        review, including but not limited to:        -   Data receiving module 10140 for receiving data from            electronic devices (e.g., video data from a camera 118, FIG.            1), and preparing the received data for further processing            and storage in the data storage database 10160;        -   Device control module 10142 for generating and sending            server-initiated control commands to modify operation modes            of electronic devices (e.g., devices of a smart home            environment 100), and/or receiving (e.g., from client            devices 504) and forwarding user-initiated control commands            to modify operation modes of the electronic devices;        -   Data processing module 10144 for processing the data            provided by the electronic devices, and/or preparing and            sending processed data to a device for review (e.g., client            devices 504 for review by a user);        -   Trigger detection module 10146 for detecting trigger events            (e.g., using optional built-in sensors and inputs of the hub            device 180, smart devices 204, and/or any other devices            connected to the network 162) and providing notifications of            detected trigger events;        -   Lock device state module 10148 for determining a target            state and current state of a lock device (e.g., smart door            lock 120, FIG. 11), and for providing instructions to the            lock device (e.g., if the target state and current state of            the lock device are not the same);        -   Security profile module 10150 for managing and storing            respective user security profiles and settings (e.g., FIG.            13C); and        -   Adjustment rule module 10152 for creating and storing            adjustment rules based on user inputs (e.g., override            inputs), where in some implementations, a target state of a            lock device is based on one or more created adjustment rules            (e.g., used by lock device state module 628); and    -   Server database 1016, including but not limited to:        -   Data storage database 10160 for storing data associated with            each electronic device (e.g., each camera) of each user            account, as well as data processing models, processed data            results, and other relevant metadata (e.g., names of data            results, location of electronic device, creation time,            duration, settings of the electronic device, etc.)            associated with the data, wherein (optionally) all or a            portion of the data and/or processing associated with the            electronic devices are stored securely; and        -   Account database 10162 for storing account information for            user accounts, including user account information,            information and settings for linked hub devices and            electronic devices (e.g., hub device identifications), hub            device specific secrets, relevant user and hardware            characteristics (e.g., service tier, device model, storage            capacity, processing capabilities, etc.), user interface            settings, data review preferences, etc., where the            information for associated electronic devices includes, but            is not limited to, one or more device identifiers (e.g., MAC            address and UUID), device specific secrets, and displayed            titles.

Each of the above identified elements may be stored in one or more ofthe previously mentioned memory devices, and corresponds to a set ofinstructions for performing a function described above. The aboveidentified modules or programs (i.e., sets of instructions) need not beimplemented as separate software programs, procedures, or modules, andthus various subsets of these modules may be combined or otherwisere-arranged in various implementations. In some implementations, memory1006, optionally, stores a subset of the modules and data structuresidentified above. Furthermore, memory 1006, optionally, storesadditional modules and data structures not described above.

Furthermore, in some implementations, the functions of any of thedevices and systems described herein (e.g., hub device 180, hub serversystem 508, client device 504, smart device 204, and/or smart homeprovider server system 164) are interchangeable with one another and maybe performed by any other devices or systems, where the correspondingsub-modules of these functions may additionally and/or alternatively belocated within and executed by any of the devices and systems. As oneexample, referring to FIG. 11, a smart camera 118-1, a smart doorbell106, and/or a smart door lock 120 detect a trigger event (e.g., motionof an unverified user 1102) on the premises of the smart homeenvironment 100, while a smart camera 118-2 and a smart hazard detector104 detect occupancy within the premises. Furthermore, in this example,a hub device 180 determines a target state of the smart door lock 120based on the inputs of the devices that detected occupancy and thetrigger event, and provides instructions to the smart door lock 120accordingly. The devices and systems shown in and described with respectto FIGS. 6-10 are merely illustrative, and different configurations ofthe modules for implementing the functions described herein are possiblein various implementations.

FIG. 11 is an example smart home environment 100, in accordance withsome implementations. In the example illustrated, the smart homeenvironment 100 consists of a structure 150 with multiple rooms 1100(e.g., rooms 1100-1 through 1100-4), throughout which a variety ofdevices (e.g., smart devices) are positioned. Devices include a smarthazard detector 104, smart appliances 112 (e.g., washing machine 112-2,television 112-2), a smart thermostat 102, smart wall switches 108, asmart wall plug 110, a hub device 180, cameras 118, a smart doorbell106, a smart door lock 120, and a smart alarm system 122. The devices inthe smart home environment 100 combine to create a mesh network throughwhich data and instructions can be exchanged between devices, andcommunication with other users, devices, and systems connected to thenetwork 162 is enabled (e.g., through a network interface 160). Forexample, devices in the smart home environment 100 may communicate with(e.g., provide notifications to, receive commands from) an authorizeduser who is not currently on the premises via a client device 504-1. Thesmart home environment 100 (or any combination of devices within thesmart home environment 100) is sometimes referred to as a “securitysystem.” Smart home environments 100 and associated devices aredescribed in greater detail with respect to FIG. 1. Thus, while somefeatures of the smart home environment 100 in FIG. 11 are discussed,other features have not been so as not to obscure more pertinent aspectsof the example implementation disclosed herein. Furthermore, while someexample devices of the smart home environment 100 are illustrated, otherimplementations of the smart home environment 100 may include fewer orother additional devices.

The example illustrates a situation in which a trigger event is detectedon the premises of the smart home environment 100. Trigger events areoccurrences detected by one or more devices (e.g., devices in a smarthome environment 100, FIGS. 1 and 11) that may or may not constitute asecurity breach. As some situations do not rise to the level of asecurity threat, it is sometimes permissible—and at times evendesirable—that a door lock device retains a current locked/unlockedstate until it is absolutely necessary to extend or retract the lock.This is particularly beneficial with respect to energy conservation,which is critical given that many smart lock devices are batteryoperated, and because actuating and retracting the bolt of a lock deviceconsumes considerable power. Thus, by determining a target state of thelock device at a particular instance (e.g., when a trigger event isdetected) and comparing the target state to a current state of the lockdevice, a determination can be made as to whether instructions should besent to either actuate (i.e., lock) or retract (i.e., unlock) the bolt.As described in greater detail below, the target state of the lockdevice may be based on several factors, such as a current premises mode(e.g., armed/disarmed), a number of occupants detected within thepremises, security profiles (i.e., profiles indicating desired targetstates when a respective user is detected), locations of detected users(e.g., particular room), and/or user states (e.g., asleep) of detectedusers. The determination of a target state based on such factors may beentirely automatic or predefined by a user.

In the example illustrated, an unverified user 1102 is detectedapproaching the front door of the smart home environment 100. Theunverified user 1102 approaching is a trigger event that is detected bythe presence detection capabilities of multiple devices positionedexternal to the structure 150, including the smart door lock 120, thesmart doorbell 106, and the camera 118-1. Upon detecting the triggerevent, one or more devices (e.g., the hub device 180) determine a targetstate of the lock device (e.g., smart door lock 120). In this example,assuming the threshold number of users to enable an “unlocked” state isfour, the target state of the lock device will be unlocked since fiveusers (e.g., users 1104-1 through 1104-5) are within the premises, anumber determined by collecting data from several devices (e.g., the hubdevice 180 for detecting user 1104-5, and camera 118-2 and/or the smartalarm system 122 for detecting users 1104-1 through 1104-4). Afterwards,the determined target state of the lock device is compared against thecurrent state of the lock device. If a discrepancy is detected (e.g.,current state of the lock device is “unlocked,” but the target state is“locked”), instructions are provided to the lock device based on thetarget state (e.g., instructions to actuate the bolt of the door lock).Thus, in situations in which the current state of the lock devicealready reflects the target state, commands will not be sent to the lockdevice. As a result, battery life is conserved and device wear isreduced.

FIG. 12 illustrates various states of a lock device, in accordance withsome implementations. Illustrated is a partial view of a door 1200 and adoor frame 1202 in which the door is situated, viewed from inside apremises. Built into the door 1200 is a door handle 1208 and a smartdoor lock 120 (the “lock device”), which includes a bolt 1206 that canbe extended (“locked”) and retracted (“unlocked”). Adjacent to the door1200 is the door frame 1202 which includes a door jamb 1206, themechanism into which the bolt 1204 extends and creates a secure latchfor locking the door 1200.

Three different states of a lock device (e.g., smart door lock 120) areillustrated, specifically states in which: (1) the bolt is retracted (afirst “unlocked” state), (2) the bolt is extended into door jamb (a“locked” state), and (3) the bolt is extended out of the (a second“unlocked” state). Solely for the purposes of illustrating these variousstates, a visible gap is shown between the door 1200 and the door jamb1206.

In most situations, it is inadequate for security purposes to simplyidentify whether the bolt of a lock device is extended or retracted. Forexample, when the bolt 1204 is extended out of the doorjamb, it isexpected that the door is in a locked state (as indicated by the“Locked” indication on the smart door lock 120 in state (3), FIG. 12),when in fact, the door is effectively unlocked. This gives rise to asecurity risk that should be brought to the attention of occupantswithin or away from the premises, especially in situations in which thelock device should be locked (i.e., the target state of the lock deviceis a “locked” state) since physical intervention would be required toproperly lock the door.

The door jamb 1206 and/or the bolt 1204 may include one or morepassive/active components for detecting whether the bolt 1204 haspartially or fully extended into the door jamb 1206. For example, theone or more passive/active components may operate jointly to form anelectrical circuit, where a short circuit would indicate that the bolt1204 has extended into the door jamb 1206, and where an open circuitwould indicate that the bolt 1204 is not extended into the door jamb1206. In some implementations, the bolt 1204 and/or the door jamb 1206include touch-sensitive components for detecting whether the bolt 1204is extended into the door jamb 1206.

As described in greater detail below, in some implementations, when thetarget state of the lock device is determined to be a locked state(i.e., state (2), FIG. 12) and it is detected that the lock device iscurrently in the second unlocked state (i.e., state (3)), instructionsare provided to the lock device which cause the bolt to be retracted,and a notification is sent to an occupant of the premises (e.g., user1104-1, FIG. 11).

FIGS. 13A-13C illustrate examples of graphical user interfaces (“GUIs”)for displaying notifications, sending commands, and managing a securityprofile, in accordance with some implementations. The GUIs in thesefigures are used to illustrate interfaces related to the processesdescribed below, including the method 1400 (FIGS. 14A-14D). While FIGS.13A-13C illustrate examples of GUIs, in other implementations, one ormore GUIs display user-interface elements in arrangements distinct fromthe implementations of FIGS. 13A-13C.

The GUIs shown in FIGS. 13A-13C may be displayed on any devices (e.g.,devices of the smart home environment 100 connected to network 162,FIGS. 1 and 11) having an output component (e.g., display, speaker,tactile feedback generator, etc.), such as mobile phones (e.g., clientdevices 504), smart devices (e.g., hub device 180, smart television112-2, FIG. 1), or other electronic devices (e.g., personal computers,tablet computers, etc.). The GUIs may be provided by an application formanaging devices of a smart home environment 100 (e.g., applications824, FIG. 8), and/or a web browser application.

FIG. 13A illustrates a GUI for displaying a notification 1300 and forsending commands to a lock device (e.g., smart door lock 120, FIG. 11).FIG. 13A merely illustrates one implementation of the method 1400 inwhich a user may receive notifications and provide commands through aGUI. In some implementations, however, at least some steps of the method1400 are automated and do not require user interaction (e.g., do notrequire authorization to lock/unlock a lock device in response todetecting a trigger event).

Referring to the example of FIG. 11, the notification 1300 in FIG. 13Aindicates that a trigger event has been detected at a smart homeenvironment 100 associated with the authorized user of the client device504. In this example, the notification 1300 indicates the particulararea and time at which the trigger event was detected (e.g., front door,11:00 PM), the type of trigger event (e.g., motion detected withinproximity), the number of detected occupants (e.g., 5), the target stateof the lock device (e.g., “unlocked”), and the current state of the lockdevice (e.g., “unlocked”). In this example, the threshold number ofoccupants for maintaining an unlocked target state of the lock device isfour occupants. Thus, because five occupants (e.g., users 1104-1 through1104-5, FIG. 11) are detected, the target state of the lock device(e.g., smart door lock 120) is an “unlocked” state. Consequently,because the current state of the lock device is also an “unlocked”state, the notification requests confirmation from the user to maintainthe unlocked state.

Various user-interface (“UP”) elements (e.g., 1302-1 to 1302-3) aredisplayed, corresponding to various operations and commands that anauthorized user may choose to execute in response to the notification1300. The user may choose to: keep the door unlocked (1302-1), lock thedoor (1302-2), or change the settings of his security profile (1302-3).

FIG. 13B illustrates a GUI that is displayed in response to theauthorized user requesting to keep the lock device unlocked (e.g.,command to keep the lock device unlocked, 1302-1, FIG. 13A).Additionally, because the user provided an override input negatinginstructions corresponding to the target state of the lock device (e.g.,command to keep the lock device unlocked, rather than lock the lockdevice), the GUI optionally prompts the user to create an adjustmentrule based on the override input. In this example, the GUI indicatesthat the user has regularly provided an override input in response totrigger events detected at that particular time of day, suggesting thepossibility that the determined target state of the lock device was notproperly determined. In some implementations, if the user chooses tocreate an adjustment rule (1312-1), the target state of the lock devicedetermined in response to a subsequent trigger event under similarcircumstances (e.g., same time of day, type of trigger event, number ofoccupants within the premises, etc.) will be set to an unlocked state,rather than a locked state. Alternatively, by foregoing the creation ofa new adjustment rule (1312-2), the target state of the lock device willcontinue to be a locked state in response to subsequent trigger eventsunder similar circumstances. Adjustment rules are described in greaterdetail with respect to the method 1400 (FIGS. 14A-14D).

FIG. 13C illustrates a GUI that is displayed in response to theauthorized user requesting to change the settings of his securityprofile (e.g., command to lock the lock device, 1302-3, FIG. 13A). Auser may configure his respective security profile to dictate under whatconditions the target state of the lock device will be locked/unlockedwhen the user is within or away from the premises.

The GUI illustrates various examples of such settings that be configuredfor a security profile (1320). For example, a user may keep the doorlocked if the user is the only occupant within the premises (1322-1), ifthe user is asleep (1322-2), or at all times (1322-3). Optionally, theuser may configure other settings related to security profiles (1322-4).Security profiles are described in greater detail with respect to FIGS.14A-14D.

FIGS. 13A-13C illustrate only examples of GUIs that may be displayed inperforming the method 1400 described below (FIGS. 14A-14D). It is noted,however, that additional and/or alternative GUIs may be displayed,including UI elements corresponding to alternative and/or additionalcommands or operations that may be executed.

FIGS. 14A-14D are flow diagrams illustrating a method of automaticallydetermining a target state of a lock device in response to detecting atrigger event, in accordance with some implementations. In someimplementations, the method 1400 is performed by one or more electronicdevices of one or more systems (e.g., devices of a smart homeenvironment 100, FIGS. 1 and 11; devices 204 and/or hub device 180 ofsmart home network 202, FIG. 2) and/or a server system (e.g., smart homeprovider server system 164 of FIGS. 1 and 2, hub server system 508 ofFIG. 5). Thus, in some implementations, the operations of the method1400 described herein are entirely interchangeable, and respectiveoperations of the method 1400 are performed by any of the aforementioneddevices, systems, or combination of devices and/or systems. For ease ofreference, the methods herein will be described as being performed by anelectronic device (e.g., hub device 180, FIG. 11) associated with a lockdevice (e.g., smart door lock 120). In some implementations, theelectronic device is the lock device (e.g., smart door lock 120). FIGS.14A-14D correspond to instructions stored in a computer memory or othercomputer-readable storage medium (e.g., memory 606 of the hub device180).

The electronic device obtains (1402) a number of users detected within apremises. Referring to the example of FIG. 11, five users (e.g., users1104-1 through 1104-5) are detected within the smart home environment100. Furthermore, the electronic device detects (1404) a trigger eventrelated to a lock device (e.g., smart door lock 120, FIG. 11) and thepremises. As noted above, trigger events are occurrences detected by oneor more devices (e.g., devices in a smart home environment 100, FIGS. 1and 11) that may or may not constitute a security breach. Premises uponwhich a trigger event may be detected include a perimeter established bythe smart home environment 100 (e.g., in a room 1100, on the front yardoutside of the structure 150, on a porch of the structure 150, etc.), orby multiple smart home environments 100 (e.g., within a geo-fenceperimeter established by multiple smart devices across multiple smarthome environments 100 within a neighborhood). Trigger events may includedetection of motion around or within the premises, such as detectingmotion within a predefined range of a structure (e.g., within 20 feet ofthe structure 150, within a 100-foot radius of the center of thestructure 150) or in a specified area of the premises (e.g., front lawn,back yard, a room 1100, etc.). Trigger events may also include detectingan applied force on the premises (e.g., touch detected on the structure150, touch detected on a door handle coupled to the smart door lock 120,etc.). In some implementations, trigger events include attemptedopenings of entryways (e.g., window, front door, garage). In someimplementations, detecting (1404) the trigger event includes detecting(1406) that an unverified user entered the premises (e.g., the smarthome environment 100 in FIG. 11, including an area surrounding thestructure 150). In some implementations, detecting the trigger eventincludes detecting that an unverified user is approaching or attemptingto enter the premises (i.e., detecting that a user is approaching,rather than breaching, a perimeter of the premises). In someimplementations, trigger events are detected by one or more sensingcapabilities of a device (or a group of devices) in the smart homeenvironment 100. For example, referring to FIG. 11, the unverified user1102 approaching the door is a trigger event that is detected based ondata gathered from the camera 118-1, the smart doorbell 106, and/or thesmart door lock 120.

In some implementations, the lock device includes (1408) a bolt (e.g.,smart door lock 120 that includes a bolt 1204, FIG. 12). The state ofthe lock device is: a locked state (1410), wherein the bolt of the lockdevice is extended into a door jamb (e.g., state (2), FIG. 12); a firstunlocked state (1412), wherein the bolt of the lock device is retracted(e.g., state (1), FIG. 12); or a second unlocked state (1414), whereinthe bolt of the lock device is extended, but not into the door jamb(e.g., state (3), FIG. 12).

Optionally, in implementations in which an unverified user is detected(step 1406), the electronic device determines (1416) whether theunverified user is an authorized user. In some implementations, whetherthe unverified user is an authorized user is determined via user inputreceived on an interactive touch-screen device (e.g., selection of aresponse on the touch-screen of the hub device 180), a biometric sample(e.g., fingerprint, retinal scan), user credentials (e.g., username andpassword, PIN), detection of an authenticated RFID device (e.g., RFIDtag), wireless pairing of an authenticated device (e.g., Wi-Fi, IR,Bluetooth, key fob), and/or any other personal identification meansknown to those skilled in the art.

When the trigger event is detected (1404), the electronic devicedetermines (1418) a target state of the lock device. The target state isa state of the lock device (e.g., locked/unlocked) that is desirablebased on circumstantial information surrounding a trigger event (e.g.,data gathered by devices within a smart home environment 100),pre-configured user settings (e.g., defined by a security profile),behavioral user information, and/or other information known or unknownto a user. In other words, the target state reflects whether theuser—given available circumstantial information surrounding a triggerevent—would want the lock device to be unlocked or locked. Furthermore,as described in greater detail below, a current state of the lock deviceis determined (1460, FIG. 14D), and if the current state and the targetstate of the lock device are not the same, instructions are provided(1462, FIG. 14D) to the lock device based on the target state.

The target state of the lock device is determined based on (1420) atleast one or a combination of factors. A non-exhaustive discussion ofsuch factors and signals is described with respect to FIG. 14B, withexamples of determined target states being described with respect toFIG. 14C (target state is a locked state, 1438) and FIG. 14D (targetstate is an unlocked state, 1452). Moreover, in some implementations,the target state of the lock device may be based on additional factorsor signals that utilize the sensory and data processing capabilities ofdevices described herein (e.g., devices of a smart home environment 100,FIGS. 1 and 11). Additional examples include hazard signals (e.g.,alerts regarding carbon monoxide levels), personal details of occupantsdetected within the premises (e.g., user IDs, age, gender, relationshipto other occupants/home owner, community status, etc.), environmentalconditions (e.g., local state of emergency, extreme weather, etc.), orother signals and/or information indicative of a risk associated with anunlocked/locked state of the lock device.

In some implementations, the target state of the lock device isdetermined based on the obtained number of users (1422) detected withinthe premises. In some implementations, the target state of the lockdevice is an unlocked state if the number of users detected within thepremises satisfies a predefined threshold (1454, FIG. 14D). For example,in FIG. 11, if the predefined threshold of detected occupants within thepremises is four, the target state of the smart door lock 120 is anunlocked state since five occupants are detected (e.g., users 1104-1through 1104-5).

In some implementations, if one or more users are detected within thepremises, the target state of the lock device is determined based onrespective security profiles (1424) of the one or more detected users,wherein a respective security profile of a respective user indicates adesired target state of the lock device when the respective user iswithin the premises. Security profile are configurable by eachindividual to dictate a desired target state (e.g., locked/unlocked) ofa lock device when the user is at home or away. An example of variousconditions that may be configured for a security profile is provided inFIG. 13C. In some implementations, security profiles indicate a type ofa respective user, where the target state of the lock device is based onthe type of the respective user (e.g., security profiles for childrenindicate that the lock device should be in a locked state at all times).In some implementations, the security profile of a respective user, ofone or more detected users, indicates (1444, FIG. 14C) that the desiredtarget state of the lock device is the locked state when the respectiveuser is within the premises (e.g., while user 1104-1 detected within thesmart home environment, target state of the smart door lock 120 is alocked state, FIG. 11). Security profiles may indicate the desired lockstate based on a user state (e.g., awake, asleep, engaged in aparticular activity). In some implementations, security profiles arespecified with respect to time, such as a particular time of day (e.g.,target state is unlocked during Monday mornings), or a thresholdduration of time for which a respective user is detected within thepremises (e.g., after a user is detected within the premises for morethan an hour, target state is locked).

In some implementations, when a plurality of users with securityprofiles are detected within the premises, the target state of the lockdevice is based on the security profile with the most stringentrequirements (e.g., the target state is a locked state if the securityprofile of any detected user indicates that the target state is lockedat all times). In some implementations, user security profiles have arespective priority, where the target state of the lock device isdetermined based on the security profile with the highest priority.

In some implementations, if one or more users are detected within thepremises, the target state of the lock device is determined based on alocation (1426) of the one or more detected users. Locations may be ageneral region of a premises (e.g., front lawn of the smart homeenvironment 100, FIG. 11) or a particular room (e.g., room 1100-1). Insome implementations, the target state of the lock device is a lockedstate if the current location of a respective user, of one or moredetected users, indicates (1438, FIG. 14C) that the respective user islocated within a predefined area of the premises. For example, anauthorized user may specify that the target state should be a lockedstate if a trigger event is detected while the user is in a specifiedroom (e.g., a bathroom, such as the room 1100-3, FIG. 11). In someimplementations, the target state of the lock device is based on adistance between a detected location of a user and the location of thedetected trigger event (e.g., the front door of the premises, FIG. 11)satisfies a predefined threshold (e.g., target state is a locked stateif distance is more than 100 feet away). In some implementations, thetarget state of the lock device is based on the average distance of allusers and the location of the trigger event is determined, and whetherthe average distance satisfied a predefined threshold.

In some implementations, if one or more users are detected within thepremises, the target state of the lock device is determined based on auser state (1428) of the one or more detected users, wherein arespective user state of a respective user indicates that the respectiveuser is asleep or active. In some implementations, the target state ofthe lock device is a locked state if the user state of a respectiveuser, of one or more detected users, indicates (1442, FIG. 14C) that therespective user is asleep. Additionally and/or alternatively, the userstate indicates a particular activity in which a respective user isengaged (e.g., target state is locked state if user is gardening,cooking, watching television, etc.).

In some implementations, the target state of the lock device isdetermined based on a current premises mode (1430), including an armedstate and a disarmed state. In some implementations, the premises modeis set manually by the user (e.g., user arms the smart alarm system 122upon leaving the premises, FIG. 11), or automatically (e.g., when smarthome environment 100 detects that a user leaves the premises). In someimplementations, the target state of the lock device is a locked stateif the current premises mode is a first armed state (1448, FIG. 14C)(e.g., an “Away” mode of a smart alarm system 122, FIG. 11), indicatingthat no authorized users are currently within the premises. In someimplementations, the target state of the lock device is a locked stateif the current premises mode is a second armed state (1450, FIG. 14C)(e.g., a “Home+Armed” mode of a smart alarm system 122, used for arminga smart home environment 100 if a user is within the premises, butasleep), indicating that at least one authorized user is currentlywithin the premises and that the lock device is configured to be in thelocked state. In some implementations, the target state of the lockdevice is an unlocked state if the current premises mode is a disarmedstate (1458, FIG. 14D) (e.g., a “Home” mode of a smart alarm system 122,FIG. 11), indicating that one authorized user is currently within thepremises and that the lock device is configured to be in the unlockedstate.

In some implementations, the target state of the lock device isdetermined based on the determination (1432) of whether the unverifieduser is an authorized user. In some implementations, the target state ofthe lock device is an unlocked state if the unverified user is (1456,FIG. 14D) an authorized user. For example, the unverified user 1102 inFIG. 11 is determined to be authorized based on detection of anauthorized key fob.

In some implementations, the target state of the lock device isdetermined based on the trigger event (1434). For example, the smarthome environment 100 (FIG. 11) may be configured such that the targetstate of the lock device remains unlocked if movement is detected aroundthe window 1106 (room 1100-2), so as to exclude expected movement ofdomestic animals from triggering a locked state.

In some implementations, determining the target state includes (1436)obtaining one or more inputs from one or more devices distinct from theelectronic device and the lock device. For example, referring to FIG.11, the number of users within the premises is detected (1402) byretrieving data from the smart hazard detector 104 and/or the hub device180 in room 1100-4 (for detecting user 1104-5), and by the smart alarmsystem 122, smart wall plug 110, smart wall switch 108, and/or camera118-2 in room 1100-1 (for detecting users 1104-1 through 1104-4).

In some implementations, the factors upon which the target state of thelock device is based (described above with respect to FIG. 14B) haverespective weights, wherein the target state of the lock device isdetermined based on the respective weights. Thus, in someimplementations, factors having greater respective weights takeprecedence over other factors with lesser respective weights withrespect to determining the target state of the lock device. As anexample, if the current premises mode (1430) has a greater respectiveweight than the weight associated with the number of users detectedwithin the premises (1422), if the current premises mode is determinedto be the second armed state (1450, FIG. 14C, a “Home+Armed” mode wherethe target state is a locked state, for example), the target state ofthe lock device will be a locked state regardless of how many users aredetected on the premises.

Referring to FIG. 14D, the electronic device determines (1460) a currentstate of the lock device. In some implementations, the current state ofthe lock device is a locked state (1410, FIG. 14A), a first unlockedstate (1412, FIG. 14A) (i.e., bolt retracted), or a second unlockedstate (1414, FIG. 14A) (i.e., bolt extended, but not into door jamb). Insome implementations, the current state of the lock device is anunlocked state (e.g., default state of the lock device is unlocked, andlock device is only locked when necessary).

If the current state (determined at 1460) of the lock device and thetarget state (determined at 1418, FIGS. 14B-14D) of the lock device arenot the same, instructions are provided (1462) to the lock device basedon the target state of the lock device. In doing so, the lock device isoperated (e.g., extending/retracting the bolt) and power is consumedonly if necessary, based on the determined target state of the lockdevice. In some implementations, the instructions cause (1464) the boltof the lock device to be extended if the current state of the lockdevice is the first unlocked state and the target state of the lockdevice is the locked state (i.e., the lock device is currently unlockedand should be locked). In some implementations, the instructions cause(1466) the bolt of the lock device to be retracted if the current stateof the lock device is the locked state and the target state of the lockdevice is the first unlocked state (i.e., the lock device is currentlylocked and should be unlocked). In some implementations, theinstructions cause (1468) the bolt of the lock device to be retracted ifthe current state of the lock device is the second unlocked state andthe target state of the lock device is the locked state (i.e., the lockdevice is currently in a faulty lock position (e.g., bolt extended, butnot into the doorjamb) and should be locked, so bolt is firstretracted). Optionally, a notification regarding the current state ofthe lock device (e.g., the second unlocked state) is sent to one or moreusers so that the lock device may be properly secured.

In some implementations, if the current state of the lock device and thetarget state of the lock device are not the same, prior to providing theinstructions to the lock device (1462), a notification is providedindicating that the current state and the target state are not the same.Subsequently, an override input is received (e.g., if instructions arebased on a locked target state, the override input corresponds to anunlocked target state), wherein the instructions provided to the lockdevice are further based on the override input (e.g., instructions tomaintain current state of lock device). Prior to engaging the targetstate of the lock device, a user is therefore given the opportunity todecide whether the automatically determined target state is desirable,and may send an override command to toggle the target state. An exampleGUI for providing a notification (e.g., notification 1300) and forreceiving an override input (e.g., 1302-1, for toggling the target statefrom locked to unlocked) is illustrated in and described with respect toFIG. 13A. Additionally and/or alternatively, an override input includesthe manual extension or retraction of a bolt of the lock device by auser (e.g., toggling the latch of a smart door lock 120, FIG. 12). Insome implementations, the notification is provided and the overrideinput is received after the instructions (based on the target state ofthe lock device) have been provided to the lock device. In someimplementations, a notification is provided indicating that the currentstate and the target state of the lock device are the same, and theoverride input is received in response to the notification (e.g., totoggle target state from unlocked to locked, or locked to unlocked).

In some implementations, after receiving an override input, anadjustment rule is created in accordance with the override input. Aftercreating the adjustment rule, when a subsequent trigger event isdetected, a subsequent target state of the lock device is determinedbased on at least the adjustment rule. An example is illustrated inFIGS. 13A and 13B. Here, the user provided an override input for keepingthe lock device unlocked (1302-1). As the notification in FIG. 13Bindicates, the user is prompted with a request to create an adjustmentrule based on the user's observed pattern for keeping the lock deviceunlocked during the particular time of day at which the trigger eventwas detected (e.g., 11:00 PM, FIG. 13A). Accordingly, if the userchooses to create an adjustment rule, the target state of the lockdevice determined for subsequent trigger events of the same or similarnature (e.g., movement detected at the front door around 11:00 PM) willbe based on the adjustment rule (e.g., the target state will be anunlocked state, as opposed to a locked state). Adjustment rulestherefore dynamically track and adapt to user behavior, and allow forthe calibration and refinement of algorithms used for determining thetarget state of the lock device. In some implementations, machinelearning techniques known to those skilled in the art are used forautomatically creating the adjustment rules. In some implementations,the adjustment rule includes details with respect to the parameters uponwhich the initial target state was determined (e.g., the initial targetstate, determined prior to creating the adjustment rule, was based on athreshold of five users detected within the premises). In someimplementations, the adjustment rule is created when a threshold numberof override inputs has been received with respect to a plurality oftrigger events having similar corresponding circumstances (e.g.,override inputs are received for five separate trigger events in whichmotion was detected at the front door at 11:00 PM while five occupantswere detected within the premises). In some implementations, theadjustment rule is created when an override input is received within apredefined window of time after instructions based on the target stateare provided, so as to avoid tracking of lock state toggles that do notsuggest that the target state was inaccurately determined (e.g., onlylock toggles occurring within 1 minute after instructions are providedto the lock device are considered override inputs with respect tocreating an adjustment rule).

As stated above, operations of the method 1400 described herein areentirely interchangeable and may be performed by different devices orthe same device. For example, a smart device in the vicinity having agreater number of interconnections with nearby smart devices, moreprocessing power, Internet connectivity, and a persistent power source(e.g., a hub device 180) may be better suited for determining a targetstate of the lock device. In other implementations, given the limitedstorage space of some smart devices, it may be preferable that a remoteserver system (e.g., smart home provider server system 164) stores anddetermines appropriate target states of the lock device. In otherimplementations, however, the lock device itself manages its own statewithout requiring the additional processing power and storagecapabilities of other devices. In some implementations, a determinationof where and by which devices operations are performed is based oncurrent or changing environmental conditions (e.g., in the event of apower outage, the task of determining the target lock state is delegatedto the lock device, assuming it is battery-operated).

For situations in which the systems discussed above collect informationabout users, the users may be provided with an opportunity to opt in/outof programs or features that may collect personal information (e.g.,information about a user's preferences or usage of a smart device). Inaddition, in some implementations, certain data may be anonymized in oneor more ways before it is stored or used, so that personallyidentifiable information is removed. For example, a user's identity maybe anonymized so that the personally identifiable information cannot bedetermined for or associated with the user, and so that user preferencesor user interactions are generalized (for example, generalized based onuser demographics) rather than associated with a particular user.

Although some of various drawings illustrate a number of logical stagesin a particular order, stages that are not order dependent may bereordered and other stages may be combined or broken out. While somereordering or other groupings are specifically mentioned, others will beobvious to those of ordinary skill in the art, so the ordering andgroupings presented herein are not an exhaustive list of alternatives.Moreover, it should be recognized that the stages could be implementedin hardware, firmware, software or any combination thereof.

The foregoing description, for purpose of explanation, has beendescribed with reference to specific implementations. However, theillustrative discussions above are not intended to be exhaustive or tolimit the scope of the claims to the precise forms disclosed. Manymodifications and variations are possible in view of the aboveteachings. The implementations were chosen in order to best explain theprinciples underlying the claims and their practical applications, tothereby enable others skilled in the art to best use the implementationswith various modifications as are suited to the particular usescontemplated.

What is claimed is:
 1. A method, comprising: at an electronic devicehaving one or more processors and memory for storing instructions forexecution by the one or more processors, wherein the electronic deviceis associated with a lock device: obtaining a determination that one ormore users are within a premises; detecting a trigger event related tothe lock device and the premises; in response to detecting the triggerevent, determining that a target state of the lock device is a lockedstate based on: a current location of a user, of the one or more users,within a predefined area of the premises; and a security profileassociated with the premises; determining a current state of the lockdevice; and if the current state of the lock device and the target stateof the lock device are not the same, providing instructions to the lockdevice based on the target state of the lock device.
 2. The method ofclaim 1, wherein determining the target state of the lock deviceincludes obtaining one or more inputs from one or more devices distinctfrom the electronic device and the lock device.
 3. The method of claim1, wherein detecting the trigger event includes detecting that anunverified user entered the premises.
 4. The method of claim 3, furthercomprising: after detecting the trigger event: determining whether theunverified user is an authorized user, wherein determining the targetstate of the lock device is further based on the determination ofwhether the unverified user is an authorized user.
 5. The method ofclaim 1, wherein the lock device includes a bolt, and wherein a state ofthe lock device is: a locked state, wherein the bolt of the lock deviceis extended into a door jamb; a first unlocked state, wherein the boltof the lock device is retracted; or a second unlocked state, wherein thebolt of the lock device is extended, but not into the door jamb.
 6. Themethod of claim 5, wherein the instructions cause the bolt of the lockdevice to be extended if the current state of the lock device is thefirst unlocked state and the target state of the lock device is thelocked state.
 7. The method of claim 5, wherein the instructions causethe bolt of the lock device to be retracted if the current state of thelock device is the second unlocked state and the target state of thelock device is the locked state.
 8. The method of claim 1, wherein thedetermination that the target state of the lock device is the lockedstate is further based on a security profile of a respective user, ofthe one or more detected users, indicating that the desired target stateof the lock device is the locked state when the respective user iswithin the premises.
 9. The method of claim 1, wherein the determinationthat the target state of the lock device is the locked state is furtherbased on a user state of a respective user, of the one or more detectedusers, indicating that the respective user is asleep.
 10. The method ofclaim 1, wherein the determination that the target state of the lockdevice is the locked state is further based on one or more of: a currentpremises mode being in a first armed state indicating that no authorizedusers are currently within the premises; and the current premises modebeing in a second armed state, indicating that at least one authorizeduser is currently within the premises.
 11. The method of claim 1,further comprising: determining that the current state of the lockdevice and the target state of the lock device are not the same; and inresponse to the determination that the current state of the lock deviceand the target state of the lock device are not the same and prior toproviding the instructions to the lock device: providing a notificationindicating that the current state and the target state are not the same;and in response to the notification, receiving user input, wherein theinstructions provided to the lock device are further based on the userinput.
 12. The method of claim 11, further comprising: creating anadjustment rule in accordance with the user input; detecting asubsequent trigger event; and when the subsequent trigger event isdetected, determining a subsequent target state of the lock device basedon at least the adjustment rule.
 13. The method of claim 1, whereindetermining the target state of the lock device is further based on thetrigger event.
 14. The method of claim 1, wherein the current state ofthe lock device is an unlocked state.
 15. An electronic deviceassociated with a lock device, comprising: a processor; and memory forstoring one or more programs for execution by the processor, the one ormore programs including instructions for: obtaining a determination thatone or more users are within a premises; detecting a trigger eventrelated to an associated lock device and the premises; in response todetecting the trigger event, determining that a target state of the lockdevice is a locked state based on: a current location of a user, of theone or more users, within a predefined area of the premises; and asecurity profile associated with the premises; determining a currentstate of the lock device; and if the current state of the lock deviceand the target state of the lock device are not the same, providinginstructions to the lock device based on the target state of the lockdevice.
 16. A non-transitory computer readable storage medium, storingone or more programs for execution by one or more processors, the one ormore programs including instructions for: obtaining a determination thatone or more users are within a premises; detecting a trigger eventrelated to an associated lock device and the premises; in response todetecting the trigger event, determining that a target state of the lockdevice is a locked state based on: a current location of a user, of theone or more users, within a predefined area of the premises; and asecurity profile associated with the premises; determining a currentstate of the lock device; and if the current state of the lock deviceand the target state of the lock device are not the same, providinginstructions to the lock device based on the target state of the lockdevice.
 17. The non-transitory computer readable storage medium of claim16, wherein the trigger event includes one or more of: detected motionby an unverified user; detected contact with a surface on the premises;and detected interaction with an entryway of the premises.
 18. Thenon-transitory computer readable storage medium of claim 16, wherein thedetermination that the target state of the lock device is the lockedstate is further based on a time at the premises.
 19. The non-transitorycomputer readable storage medium of claim 16, wherein the predefinedarea of the premises includes one or more of: a bedroom; a bathroom; ayard; and an area that is greater than a threshold distance from asource of the trigger event.
 20. The non-transitory computer readablestorage medium of claim 16, wherein the determination that the targetstate of the lock device is the locked state is further based on alocation of the trigger event.